Skip to content

publish rust: semver option#28

Merged
grod220 merged 1 commit into
mainfrom
semver-option
Apr 2, 2026
Merged

publish rust: semver option#28
grod220 merged 1 commit into
mainfrom
semver-option

Conversation

@grod220
Copy link
Copy Markdown
Member

@grod220 grod220 commented Apr 2, 2026

Provides consumers the ability to opt out of semver checks.

Relevant to https://github.com/solana-program/libraries/actions/runs/23888453532 where it's attempting a version that knowingly does not pass the check.

@grod220 grod220 requested a review from joncinque April 2, 2026 09:16
Copy link
Copy Markdown
Contributor

@joncinque joncinque left a comment

Choose a reason for hiding this comment

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

Looks good to me! And since we'll need to update the downstream repos to pass it, making it not required makes the most sense too.

Just a question on the check, but not blocking this change


- name: Check semver
if: ${{ steps.has_lib.outputs.has_lib == 'true' }}
if: ${{ steps.has_lib.outputs.has_lib == 'true' && inputs.run-semver }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm never sure how yaml works to be honest, but in the sdk we do inputs.run-semver == 'true' -- do we not need to be that pedantic?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The docs says that "inputs context preserves Boolean values as Booleans".

But for outputs "steps.<step_id>.outputs.<output_name>: string. So this strange looking mixed expression is correct.

@grod220 grod220 merged commit e3681ca into main Apr 2, 2026
@grod220 grod220 deleted the semver-option branch April 2, 2026 09:40
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