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

clang-uml 0.5.5 #192599

Merged
merged 2 commits into from
Oct 2, 2024
Merged

clang-uml 0.5.5 #192599

merged 2 commits into from
Oct 2, 2024

Conversation

BrewTestBot
Copy link
Member

Created by brew bump


Created with brew bump-formula-pr.

@github-actions github-actions bot added the bump-formula-pr PR was created using `brew bump-formula-pr` label Oct 2, 2024
- switch to latest `llvm`
- try removing some workarounds
- remove `caveats`; they're not Homebrew-specific

Signed-off-by: Carlo Cabrera <[email protected]>
Copy link
Contributor

github-actions bot commented Oct 2, 2024

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Oct 2, 2024
@BrewTestBot BrewTestBot added this pull request to the merge queue Oct 2, 2024
Merged via the queue into master with commit 8ef4877 Oct 2, 2024
15 checks passed
@BrewTestBot BrewTestBot deleted the bump-clang-uml-0.5.5 branch October 2, 2024 11:20
@bkryza
Copy link
Contributor

bkryza commented Oct 2, 2024

@carlocab Hi, I'm the author of clang-uml - I've just released 0.5.5 few minutes ago and noticed it's already been in Homebrew for 7 hours - so thank you :-) Just out of curiosity, is a PR to bump the version generated automatically whenever I push a tagged commit?

My workflow is as follows:

  1. Create a release branch (e.g. v0.5.5)
  2. Prepare the release in that branch, update docs, run tests, etc.
  3. Tag the latest commit and push to that release branch (e.g. 0.5.5)
  4. Build packages for Ubuntu, Fedora, Windows and check building on macos
  5. If something is wrong, fix the code, retag, push the tag again and rebuild all packages
  6. Finally when all packages are built, publish the release on GitHub
  7. Merge the release branch to master

The only issue is that if there is something to fix during release procedure, the macos version might differ from the tag in GitHub. I'll try to remember that for next releases and not push the tag until the very last moment...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants