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

Add publish-check-compile workflow #6556

Merged
merged 6 commits into from
Dec 3, 2024
Merged

Add publish-check-compile workflow #6556

merged 6 commits into from
Dec 3, 2024

Conversation

Morganamilo
Copy link
Contributor

Add publish-check-compile workflow

This Applies staged prdocs then configures crate deps to pull from
crates.io for our already published crates and local paths for
things to be published. Then runs cargo check on the result.

This results in a build state consitent with that of publish time and
should catch compile errors that we would of otherwise ran into mid
pubish.

This acts as a supplement to the check-semver job. check-semver works on
a high level and judges what changes are incorrect and why. This job
just runs the change, sees if it compiles, and if not spits out
a compile error.

@Morganamilo Morganamilo added A1-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). R0-silent Changes should not be mentioned in any release notes labels Nov 20, 2024
@Morganamilo Morganamilo force-pushed the check-build-ci branch 5 times, most recently from a7580b8 to 280349e Compare November 21, 2024 14:18
This Applies staged prdocs then configures crate deps to pull from
crates.io for our already published crates and local paths for
things to be published. Then runs cargo check on the result.

This results in a build state consitent with that of publish time and
should catch compile errors that we would of otherwise ran into mid
pubish.

This acts as a supplement to the check-semver job. check-semver works on
a high level and judges what changes are incorrect and why. This job
just runs the change, sees if it compiles, and if not spits out
a compile error.
@Morganamilo Morganamilo force-pushed the check-build-ci branch 2 times, most recently from dee899f to da0273b Compare November 22, 2024 23:41
@Morganamilo Morganamilo marked this pull request as ready for review November 27, 2024 10:51
@Morganamilo Morganamilo requested review from a team as code owners November 27, 2024 10:51
@paritytech-review-bot paritytech-review-bot bot requested a review from a team December 3, 2024 11:16
@Morganamilo Morganamilo added this pull request to the merge queue Dec 3, 2024
Merged via the queue into master with commit 896c814 Dec 3, 2024
199 of 204 checks passed
@Morganamilo Morganamilo deleted the check-build-ci branch December 3, 2024 14:08
Krayt78 pushed a commit to Krayt78/polkadot-sdk that referenced this pull request Dec 18, 2024
Add publish-check-compile workflow

This Applies staged prdocs then configures crate deps to pull from
crates.io for our already published crates and local paths for
things to be published. Then runs cargo check on the result.

This results in a build state consitent with that of publish time and
should catch compile errors that we would of otherwise ran into mid
pubish.

This acts as a supplement to the check-semver job. check-semver works on
a high level and judges what changes are incorrect and why. This job
just runs the change, sees if it compiles, and if not spits out
a compile error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A1-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants