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

version bump #103

Merged
merged 3 commits into from
Jul 29, 2024
Merged

version bump #103

merged 3 commits into from
Jul 29, 2024

Conversation

omarandlorraine
Copy link
Collaborator

this PR bumps the version to 0.6.0

@omarandlorraine
Copy link
Collaborator Author

$ git ls-remote --tags origin
9da44b8ae06292d9adb70c7cce31f1b034c2be50	refs/tags/v0.6.0

It seems the only tag present on the remote is the one I pushed. Is this correct?

@omarandlorraine omarandlorraine linked an issue Jul 29, 2024 that may be closed by this pull request
@mre
Copy link
Owner

mre commented Jul 29, 2024

yup, you're right.

@mre mre merged commit 4071024 into master Jul 29, 2024
8 checks passed
@mre mre deleted the v060 branch July 29, 2024 11:13
@mre
Copy link
Owner

mre commented Aug 11, 2024

I forgot to mention this, but the easiest way to create a tag is through releases:
https://github.com/mre/mos6502/releases

You can look at the existing release that I created here:
https://github.com/mre/mos6502/releases/tag/v0.6.0

Here's the schema I usually follow:

Tag: v0.6.0
Headline: Version v0.6.0

Here's the settings for the next release:

image

The coolest thing is "Generate release notes". This is what renders all changes neatly.

Apart from that, thanks for cutting the release! It really helps.

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.

We need a version bump
2 participants