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

fix(release) publish crates on nearcore release #11318

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

VanBarbascu
Copy link
Contributor

Run the publish crates WF on release.

@VanBarbascu VanBarbascu requested a review from a team as a code owner May 15, 2024 14:18

- name: Checkout nearcore repository
if: ${{ github.event_name != 'workflow_dispatch'}}
uses: actions/checkout@v4
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@andrei-near, can you confirm that this will pickup the right branch/tag when it is triggered by the release?

Copy link

codecov bot commented May 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.03%. Comparing base (ff2385d) to head (e3a9e83).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11318      +/-   ##
==========================================
+ Coverage   71.01%   71.03%   +0.01%     
==========================================
  Files         782      782              
  Lines      156476   156476              
  Branches   156476   156476              
==========================================
+ Hits       111123   111147      +24     
+ Misses      40525    40503      -22     
+ Partials     4828     4826       -2     
Flag Coverage Δ
backward-compatibility 0.24% <ø> (ø)
db-migration 0.24% <ø> (ø)
genesis-check 1.40% <ø> (ø)
integration-tests 37.17% <ø> (+0.01%) ⬆️
linux 69.08% <ø> (+<0.01%) ⬆️
linux-nightly 70.48% <ø> (+<0.01%) ⬆️
macos 52.52% <ø> (-0.01%) ⬇️
pytests 1.62% <ø> (ø)
sanity-checks 1.41% <ø> (ø)
unittests 65.47% <ø> (+0.01%) ⬆️
upgradability 0.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@frol
Copy link
Collaborator

frol commented Jun 4, 2024

This direction looks great to me. I want to highlight that previously we observed the following issues with the release pipeline:

  1. The job did not fail when the crates of the version is already published, so if version is not updated in Cargo.toml, we will have "successful" run, which did nothing in fact
  2. The versioning could be confusing to someone new to the process - we need a clear and simple rule of thumb documented in Cargo.toml regarding the versioning scheme - bump 0.x.* to 0.(x+1).0 on nearcore release since nearcore does not guarantee semver compatibility for crate interfaces yet

@@ -11,20 +13,29 @@ on:
jobs:
publish-cargo-crates:
name: "Publish near-workspaces on crates.io https://crates.io/crates/near-workspaces"
runs-on: "ubuntu-22.04-16core"
runs-on: "ubuntu-20.04-16core"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a reason for reverting this to an older version? IIRC 20.04 is nearing EOL.

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.

None yet

3 participants