Skip to content

Update release steps to include prolocation notification #2035

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

Open
mxsasha wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update release steps to include prolocation notification #2035

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 4 additions & 2 deletions documentation/github_release_steps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ code changes for the next release are already in the main branch.
1. Use tag 'vx.x.x' e.g., v1.2.3 for the release
2. Use release title: x.x.x
3. For the description use the contents of the Changelog.md for this release
6. Update the Changelog.md for the next release and commit with something like:
6. Inform prolocation that we are deploying, it may trigger their alerting.
7. Deploy.
7. Update the Changelog.md for the next release and commit with something like:

@bwbroersma bwbroersma Apr 21, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the second 7. be numbered 8. ? If so, Done should be changed to 9.

"- Bump for next version.".
7. Done.
8. Done.