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

ci: ensure Cargo.toml and CHANGELOG of published crates are updated #4620

Merged
merged 18 commits into from
Oct 14, 2023

Conversation

thomaseizinger
Copy link
Contributor

Description

Resolves: #4367.

Notes & open questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

@thomaseizinger thomaseizinger marked this pull request as draft October 10, 2023 08:16
@thomaseizinger thomaseizinger marked this pull request as ready for review October 10, 2023 10:27
mergify bot pushed a commit that referenced this pull request Oct 13, 2023
Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

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

Neat! As always, much appreciated Thomas!

scripts/ensure-version-bump-and-changelog.sh Show resolved Hide resolved
scripts/ensure-version-bump-and-changelog.sh Show resolved Hide resolved
@mergify mergify bot merged commit 0446068 into master Oct 14, 2023
73 checks passed
@mergify mergify bot deleted the feat/ci-for-manifest-and-changelog branch October 14, 2023 09:45
@mxinden mxinden mentioned this pull request Oct 16, 2023
4 tasks
mergify bot pushed a commit that referenced this pull request Oct 17, 2023
We introduced a lint in #4620 that ensures the changelog is updated when we touch a certain crate. This however leads to many "false-positives" where a change to the source code is not actually worth mentioning in the changelog.

To opt out of this change, this patch adds a condition to the job that checks for a `internal:$crate` label and if that is applied, it doesn't run the lint.

Pull-Request: #4673.
mergify bot pushed a commit that referenced this pull request Nov 20, 2023
At the moment, we have to send a separate PR that removes the `- unreleased` suffix in `CHANGELOG.md` before we can make a release. This is annoying and unnecessarily delays being able to make releases for features that have been merged into master.

As of #4620, we have CI checks that ensure we add a changelog entry when a particular crate is modified. Additionally, the CI check also ensures we bump the version in case the top-most one of the changelog is already released.

The combination of these checks should ensure that we add a section for the new version in case the top-most one is already released. Previously, the presence of `- unreleased` would notify us of that.

In the future, we can add a CI job that allows us to release at the press of a button (think `workflow_dispatch`). Until then, this setup should already make it much easier to release crates.

Pull-Request: #4894.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ci: ensure we bump crate versions for "release worthy" changes
2 participants