Skip to content

chore(release): v2.0.0 - #1783

Open
plc-automated-release[bot] wants to merge 1 commit into
masterfrom
release/next
Open

plc-automated-release[bot] wants to merge 1 commit into
masterfrom
release/next

Conversation

@plc-automated-release

@plc-automated-release plc-automated-release Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Release v2.0.0

Bumps all workspace packages from v1.1.0-dev → v2.0.0.

Review the updated CHANGELOG.md for a full list of changes.


Merge this PR to trigger tagging and GitHub release creation.

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown

Release Preview

This is the GitHub release that would be published if this PR were merged now.

  • Title: RuSTy PLC Compiler 2.0.0
  • Tag: v2.0.0
  • Previous tag: v1.0.0
Rendered release

RuSTy PLC Compiler 2.0.0

This release publishes v2.0.0.

Below is the changelog since v1.0.0.

2.0.0 - 2026-09-17

Added

Fixed

Refactored

Documentation

Expected release assets

Assets are uploaded asynchronously from the post-merge Build Linux and Build Windows runs on master.

  • plc-linux-x86_64
  • plc-linux-aarch64
  • plc.exe
  • plc-compiler_2.0.0-1_amd64.deb
  • plc-compiler_2.0.0-1_arm64.deb
  • plc-stdlib_2.0.0-1_amd64.deb
  • plc-stdlib_2.0.0-1_arm64.deb
  • stdlib-2.0.0.tar.gz
  • iec61131std.dll
  • iec61131std.lib

Linux packages prefer the native build for each target architecture.

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown

Build Artifacts

🐧 Linux

Artifact Link Size
plc-x86_64 Download 43.6 MB
stdlib Download 32.6 MB
deb-x86_64 Download 38.5 MB
schema Download 0.0 MB
plc-aarch64 Download 43.4 MB
deb-aarch64 Download 30.9 MB

From workflow run

🪟 Windows

Artifact Link Size
plc.exe Download 38.4 MB
stdlib.lib Download 4.0 MB
stdlib.dll Download 0.1 MB

From workflow run

@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 2 times, most recently from 7ec707d to 61ec38f Compare June 29, 2026 14:42
@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 9 times, most recently from 32c70d1 to ef12735 Compare July 16, 2026 09:10
@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 9 times, most recently from 17fdb7e to 50a647f Compare July 27, 2026 11:35
@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 3 times, most recently from a6b0c42 to 91e59ed Compare July 29, 2026 08:36
@plc-automated-release plc-automated-release Bot changed the title chore(release): v1.1.0 chore(release): v2.0.0 Jul 29, 2026
@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 7 times, most recently from b9e96e0 to 0381061 Compare September 1, 2026 07:24
@plc-automated-release
plc-automated-release Bot force-pushed the release/next branch 10 times, most recently from c0bc121 to 5f1999a Compare September 10, 2026 08:56
@github-actions

Copy link
Copy Markdown

1 finding in 5m 8s for $0.14 between 43b9e67 (master) and 5f1999a (release/next):

  • P3 CHANGELOG.md:78: The generated changelog now jumps from 2.0.0 directly to 1.0.0, deleting the existing 1.0.1 release entry even though tag v1.0.1 is present in the repository. This loses the release-specific history for users looking up that published version; retain the 1.0.1 section instead of folding its fix into 2.0.0.

@github-actions

Copy link
Copy Markdown

1 finding in 3m 29s for $0.10 between f216425 (master) and 33855ca (release/next):

  • P2 CHANGELOG.md:79: The release changelog drops the existing v1.0.1 section entirely, jumping from the new v2.0.0 section straight to v1.0.0. Since v1.0.1 is an already released tag, this removes its release-specific history from the canonical changelog; retain that section below v2.0.0.

@github-actions

Copy link
Copy Markdown

1 finding in 3m 9s for $0.10 between 1cdbb74 (master) and 04a30e8 (release/next):

@github-actions

Copy link
Copy Markdown

1 finding in 3m 0s for $0.09 between c4a01d3 (master) and a1498aa (release/next):

  • P2 CHANGELOG.md:5: The new 2.0.0 section replaces the existing 1.0.1 section instead of being added before it, so the changelog no longer documents the released v1.0.1 (including its release date and notes). Preserve the 1.0.1 section below the 2.0.0 notes.

@github-actions

Copy link
Copy Markdown

1 finding in 3m 46s for $0.12 between 44b84d6 (master) and b2e0e9b (release/next):

@github-actions

Copy link
Copy Markdown

1 finding in 3m 22s for $0.08 between 12d5d3a (master) and f28ce55 (release/next):

  • P2 CHANGELOG.md:83: The generated changelog drops the existing v1.0.1 release: after v2.0.0 it jumps directly to v1.0.0, even though v1.0.1 is a released tag and was documented before this change. Its fix is also repeated in the v2.0.0 list at line 71, so users get both an incorrect release attribution and no v1.0.1 history; preserve the prior section when adding the new release.

@github-actions

Copy link
Copy Markdown

1 finding in 2m 51s for $0.10 between e147785 (master) and f4d4d46 (release/next):

  • P3 CHANGELOG.md:84: The release update removes the existing v1.0.1 section and jumps from v2.0.0 to v1.0.0. Although the fix text is repeated under v2.0.0, the published v1.0.1 release and its date are no longer represented, so the changelog loses an entry from the release history; retain the v1.0.1 section below the new release.

@github-actions

Copy link
Copy Markdown

1 finding in 4m 36s for $0.14 between 931f4ef (master) and 404806d (release/next):

  • P3 CHANGELOG.md:5: This replaces the existing v1.0.1 section instead of adding v2.0.0 above it, so the released v1.0.1 notes and link disappear even though that tag remains available. Retain the prior release section below the new entry.

@github-actions

Copy link
Copy Markdown

1 finding in 3m 53s for $0.10 between e72bfbe (master) and dea3ac8 (release/next):

@github-actions

Copy link
Copy Markdown

2 findings in 5m 30s for $0.13 between bf5e6a1 (master) and f234de9 (release/next):

  • P2 book/user/building/compiling.md:102: The release bumps the compiler to 2.0.0, but the documented .comment sample still identifies plc version 1.1.0-dev; output from this branch no longer agrees with the example. Update the sample (including its date/hash) or label it explicitly as output from an older compiler.
  • P2 CHANGELOG.md:4:1: The new top section replaces the existing v1.0.1 release entry, so the published v1.0.1 link and its release notes disappear from the changelog; the hwmap fix is now attributed to v2.0.0 instead. Preserve the v1.0.1 section below v2.0.0 so the release history remains accurate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant