Skip to content

Fix code generation with multiversion feature and release v0.3.1#23

Merged
robin-nitrokey merged 1 commit intomainfrom
fix-multiversion
Feb 26, 2025
Merged

Fix code generation with multiversion feature and release v0.3.1#23
robin-nitrokey merged 1 commit intomainfrom
fix-multiversion

Conversation

@robin-nitrokey
Copy link
Member

During rebasing of #19, the line that enables the LFS_MULTIVERSION feature flag not only for the compilation but also for the code generation somehow got lost. This patch updates the build script and prepares the bugfix release v0.3.1.

During rebasing of #19,
the line that enables the LFS_MULTIVERSION feature flag not only for the
compilation but also for the code generation somehow got lost.  This
patch updates the build script and prepares the bugfix release v0.3.1.
@sosthene-nitrokey
Copy link
Contributor

Once merged and released we should also yank version 0.3.0. Since this is technically a breaking change.

@robin-nitrokey
Copy link
Member Author

I don’t see the need to yank v0.3.0. In my opinion, fixing broken code can never be a breaking change. If the multiversion feature is not enabled, this is a no-op. If it is enabled, v0.3.0 does not work at all.

@robin-nitrokey robin-nitrokey merged commit 4b2b82c into main Feb 26, 2025
6 checks passed
@robin-nitrokey robin-nitrokey deleted the fix-multiversion branch February 26, 2025 15:16
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