Skip to content

Write up our release process in the wiki - #129

Merged
DJMcNab merged 5 commits into
linebender:mainfrom
DJMcNab:release-process
Oct 23, 2025
Merged

DJMcNab merged 5 commits into
linebender:mainfrom
DJMcNab:release-process

Conversation

@DJMcNab

@DJMcNab DJMcNab commented Oct 17, 2025

Copy link
Copy Markdown
Member

I've also moved the backports wiki page to this new folder.

@grebmeg grebmeg left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks for writing up this detailed release process! This is incredibly helpful and thorough!

Comment thread content/wiki/process/release.md Outdated
Anyone can prepare the release PR (although it should be an organisation member).
The PR which makes a release should *only* bump version numbers in Cargo.toml (and Cargo.lock) files, and update the changelog.

To validate the release, you can run: `cargo publish -p {crate1} -p {crate2} --dry-run`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

When publishing crates that depend on one another, should the crates without dependencies be published first, and therefore appear first in the list for the command? Last time, I didn’t use the single-line command, I published each crate individually, but had to follow that order (starting with vello_common, then the others).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The cargo publish command does the topological sort itself, I believe, so the provided order doesn't matter.

@DJMcNab
DJMcNab merged commit 048deff into linebender:main Oct 23, 2025
2 checks passed
@DJMcNab
DJMcNab deleted the release-process branch October 23, 2025 05:23
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.

2 participants