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

chore(release): publish new versions #383

Merged
merged 1 commit into from Mar 29, 2024
Merged

Conversation

mahamakifdar19
Copy link
Contributor

@mahamakifdar19 mahamakifdar19 commented Mar 29, 2024

  • @edx/frontend-enterprise-catalog-search@10.0.0
  • @edx/frontend-enterprise-hotjar@7.0.0
  • @edx/frontend-enterprise-logistration@9.0.0
  • @edx/frontend-enterprise-utils@9.0.0

Merge checklist:

  • Evaluate how your changes will impact existing consumers (e.g., frontend-app-learner-portal-enterprise, frontend-app-admin-portal, and frontend-app-enterprise-public-catalog). Will consumers safely be able to upgrade to this change without any breaking changes?
  • Ensure your commit message follows the semantic-release conventional commit message format. If your changes include a breaking change, ensure your commit message is explicitly marked as a BREAKING CHANGE so the NPM package is released as such.
  • Once CI is passing, verify the package versions that Lerna will increment to in the Github Action CI workflow logs.
    • Note: This may be found in the "Preview Updated Versions (dry run)" step in the Github Action CI workflow logs.

Post merge:

  • Verify Lerna created a release commit (e.g., chore(release): publish) that incremented versions in relevant package.json and CHANGELOG files, and created Git tags for those versions.
  • Run the Publish from package.json Github Action workflow to publish these new package versions to NPM.
    • This may be triggered by clicking the "Run workflow" option for the master branch.
  • Verify the new package versions were published to NPM (i.e., npm view <package_name> versions --json).
    • Note: There may be a slight delay between when the workflow finished and when NPM reports the package version as being published. If it doesn't appear right away in the above command, try again in a few minutes.

Copy link

codecov bot commented Mar 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.08%. Comparing base (83e8405) to head (c1796f1).
Report is 1 commits behind head on master.

❗ Current head c1796f1 differs from pull request most recent head 8329f07. Consider uploading reports for the commit 8329f07 to get more accurate results

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #383      +/-   ##
==========================================
+ Coverage   78.67%   79.08%   +0.40%     
==========================================
  Files          35       35              
  Lines         694      698       +4     
  Branches      177      179       +2     
==========================================
+ Hits          546      552       +6     
+ Misses        135      133       -2     
  Partials       13       13              

see 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 047844f...8329f07. Read the comment docs.

 - @edx/frontend-enterprise-catalog-search@10.0.0
 - @edx/frontend-enterprise-hotjar@7.0.0
 - @edx/frontend-enterprise-logistration@9.0.0
 - @edx/frontend-enterprise-utils@9.0.0
@macdiesel macdiesel merged commit c317ac0 into master Mar 29, 2024
5 checks passed
@macdiesel macdiesel deleted the automation/lerna/version branch March 29, 2024 12:26
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

2 participants