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.

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

Update release-process #841

Merged
merged 1 commit into from
Jan 3, 2025
Merged

Update release-process #841

merged 1 commit into from
Jan 3, 2025

Conversation

ptrus
Copy link
Member

@ptrus ptrus commented Dec 19, 2024

Fixes: #773

@ptrus ptrus force-pushed the ptrus/feature/release-process branch 3 times, most recently from 8bc71f3 to 3ac064f Compare December 19, 2024 09:25
- Create a new branch for the release:

```bash
git push origin "${VERSION}"
```
```bash
export VERSION=v0.0.1
git checkout -b <user>/release-${VERSION}
```
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the ordering should be

  1. checkout a new release branch git checkout -b <user>/release-${VERSION}
  2. bump the .punch_version.py
  3. make changelog
    and then merge the PR, switch to main, pull changes, and make release-tag as described :)

Copy link
Member Author

@ptrus ptrus Dec 20, 2024

Choose a reason for hiding this comment

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

  1. checkout a new release branch git checkout -b /release-${VERSION}

Sure I'll reorder "switching branch" step and running make changelog. Although the order of these two steps does not matter.

  1. bump the .punch_version.py

make changelog bumps the .punch_version.py. So if you manually bump it before running make changelog the version will be increased twice:

nexus/Makefile

Line 173 in 12a1ea7

changelog: _version-bump

@ptrus ptrus force-pushed the ptrus/feature/release-process branch from 3ac064f to f51c772 Compare December 20, 2024 07:29
@ptrus ptrus requested a review from Andrew7234 December 25, 2024 11:02
@ptrus ptrus force-pushed the ptrus/feature/release-process branch from f51c772 to 3038273 Compare January 3, 2025 09:11
@ptrus ptrus force-pushed the ptrus/feature/release-process branch from 3038273 to 88f409c Compare January 3, 2025 12:09
@ptrus ptrus merged commit 171ab2a into main Jan 3, 2025
16 checks passed
@ptrus ptrus deleted the ptrus/feature/release-process branch January 3, 2025 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document the steps for making a release
2 participants