Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add release step to update pinned charm tests #1213

Merged
merged 6 commits into from
May 30, 2024
Merged

docs: add release step to update pinned charm tests #1213

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
762d50e
Add release step to update pinned charm tests
benhoyt May 14, 2024
1ee7576
main -> default
benhoyt May 16, 2024
a9ac13b
Link github workflows dir
benhoyt May 16, 2024
ad3cd22
chore: rephrase release procedure for charm pins
dimaqq May 29, 2024
ffb4b94
chore: grammar tweaks
dimaqq May 29, 2024
951fdbb
Merge branch 'main' into pinned-charm-tests
benhoyt May 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions HACKING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,13 +293,16 @@ To make a release of the ops library, do the following:
link to the full changelog.
8. Change [version.py][ops/version.py]'s `version` to the
[appropriate string](https://semver.org/).
9. Add, commit, and push, and open a PR to get the changelog and version bump
9. Check if there's a `chore: update charm pins` auto-generated PR in the queue. If it looks
good, merge it and check that tests still pass. If needed, you can re-trigger the
`Update Charm Pins` workflow manually to ensure latest charms and ops get tested.
10. Add, commit, and push, and open a PR to get the changelog and version bump
into main (and get it merged).
10. Back in the GitHub releases page, tweak the release notes - for example,
11. Back in the GitHub releases page, tweak the release notes - for example,
you might want to have a short paragraph at the intro on particularly
noteworthy changes.
11. Have someone else in the Charm-Tech team proofread the release notes.
12. When you are ready, click "Publish". (If you are not ready, click "Save as Draft".)
12. Have someone else in the Charm-Tech team proofread the release notes.
13. When you are ready, click "Publish". (If you are not ready, click "Save as Draft".)

This will trigger an automatic build for the Python package and publish it to
[PyPI](https://pypi.org/project/ops/)) (authorisation is handled via a
Expand Down
Loading