Skip to content

fix: actually update version number #89

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

Merged
merged 1 commit into from
Apr 18, 2025
Merged

fix: actually update version number #89

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "rustac"
version = "0.6.0-rc.0"
version = "0.6.0"
edition = "2021"
publish = false

Expand Down
11 changes: 10 additions & 1 deletion RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,12 @@
# Releasing

TODO
1. Determine the next version.
We follow (to the best of our ability) [semantic versioning](https://semver.org/).
2. Create a new branch, `git checkout -b release/vX.Y.Z`
3. Update [Cargo.toml](./Cargo.toml) with the new version
4. Update and audit [CHANGELOG.md](./CHANGELOG.md)
5. `git push -u origin`
6. Open a PR
7. When merged, tag the merge commit with the version number: `git tag -as vX.Y.Z -m vX.Y.Z`
8. Push the tag: `git push origin vX.Y.Z`
9. Create a new release