chore(release): v2.0.0 - #1783
Open
plc-automated-release[bot] wants to merge 1 commit into
Open
Conversation
Release PreviewThis is the GitHub release that would be published if this PR were merged now.
Rendered releaseRuSTy PLC Compiler 2.0.0This release publishes Below is the changelog since 2.0.0 - 2026-08-03Added
Fixed
Refactored
Documentation
Expected release assetsAssets are uploaded asynchronously from the post-merge
Linux packages prefer the native build for each target architecture. |
Build Artifacts🐧 Linux
From workflow run 🪟 Windows
From workflow run |
plc-automated-release
Bot
force-pushed
the
release/next
branch
2 times, most recently
from
June 29, 2026 14:42
7ec707d to
61ec38f
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
from
July 3, 2026 07:11
61ec38f to
12b02d5
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
9 times, most recently
from
July 16, 2026 09:10
32c70d1 to
ef12735
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
9 times, most recently
from
July 27, 2026 11:35
17fdb7e to
50a647f
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
3 times, most recently
from
July 29, 2026 08:36
a6b0c42 to
91e59ed
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
from
July 29, 2026 09:54
91e59ed to
2f66c66
Compare
plc-automated-release
Bot
changed the title
plc-automated-release
Bot
force-pushed
the
release/next
branch
2 times, most recently
from
July 30, 2026 12:18
93e7702 to
45a0bb8
Compare
plc-automated-release
Bot
force-pushed
the
release/next
branch
from
August 3, 2026 15:29
45a0bb8 to
6fba267
Compare
byteatom
pushed a commit
to byteatom/rusty
that referenced
this pull request
Aug 4, 2026
… parsing (PLC-lang#1835) ## Problem The release automation proposed **v1.1.0** (PLC-lang#1783) even though a breaking change (PLC-lang#1801, `feat!:`) landed on master since v1.0.0. The squash commit subject of PLC-lang#1801 is literally ` feat!: changed time to unsigned 32-bit preserving ltime as 64-bit (PLC-lang#1801)` — the PR title carried a leading space. A subject that doesn't start with the type fails conventional-commit parsing, and with `filter_unconventional = true` git-cliff drops the commit entirely: it neither counts toward the version bump nor appears in the generated `CHANGELOG.md`. `protect_breaking_commits` can't help because the commit is never recognized as breaking in the first place. ## Fix Add a `commit_preprocessors` entry that strips leading whitespace from the message before parsing. ## Verification On current master with this change, `git-cliff --bumped-version` reports `v2.0.0` (previously `v1.1.0`), and `git-cliff --unreleased` again lists "Changed time to unsigned 32-bit preserving ltime as 64-bit (PLC-lang#1801)". Isolated behavior confirmed in a scratch repo: `fix:` only → v1.0.1; adding `" feat!:"` (leading space) → still v1.0.1; same subject without the space → v2.0.0. Once this lands, the next master push regenerates the release PR as **v2.0.0** with the breaking change restored in the changelog. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v2.0.0
Bumps all workspace packages from v1.1.0-dev → v2.0.0.
Review the updated
CHANGELOG.mdfor a full list of changes.Merge this PR to trigger tagging and GitHub release creation.