Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

fix(ci): fix the release workflows for the stable release #3583

Merged
merged 1 commit into from
Nov 8, 2022

Conversation

leops
Copy link
Contributor

@leops leops commented Nov 8, 2022

Summary

This PR makes a few changes to the release workflows before the stable release:

  • Publish releases to the rome npm package under the latest tag instead of next
  • Ensure the prerelease environment variable is correctly exported in CLI nightly builds
  • Publish the js-api using its path instead of package name

Test Plan

Test run of the release_cli workflow: https://github.com/rome/tools/actions/runs/3418383900
Test run of the release_js_api workflow: https://github.com/rome/tools/actions/runs/3418397143

@leops leops requested a review from a team November 8, 2022 10:13
@netlify
Copy link

netlify bot commented Nov 8, 2022

Deploy Preview for docs-rometools canceled.

Name Link
🔨 Latest commit d1c34a4
🔍 Latest deploy log https://app.netlify.com/sites/docs-rometools/deploys/636a2bd5ca150400087f97ff

Comment on lines -50 to -51
env:
prerelease: true
Copy link
Contributor

Choose a reason for hiding this comment

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

Interesting: Does env only apply to the current step? Can you double check the lsp release, it uses env: too

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes it seems the env attribute is scoped to whatever "build object" it's specified on, so here it was only defined for this specific step. In the LSP workflow env is specified for the whole build jobs so it should work correctly

@leops leops merged commit 211540d into main Nov 8, 2022
@leops leops deleted the fix/ci-release branch November 8, 2022 12:48
jeysal added a commit to jeysal/rometools that referenced this pull request Nov 8, 2022
* upstream/main:
  fix(ci): fix the release workflows for the stable release (rome#3583)
  Fix logo container margin
  Fix mobile docs regressions
  perf: End-to-end Linter and Formatter benchmarks (rome#3570)
  doc: VS Code extension (rome#3579)
  refactor(rome_cli): refactor the threading of parallel traversal to increase occupancy (rome#3577)
  [docs] Add navigation dropdown for docs (rome#3578)
  doc(rome_cli): Document `--files-max-size` option
  perf(rome_js_semantic): Use FX Hash function (rome#3565)
  fix(rome_js_analyzer): `noInvalidConstructorSuper` false positive for class expressions (rome#3561)
  Clean up mobile navigation
  doc(website): Run `cargo lintdoc` (rome#3567)
  doc: Fix install command
  Fix mobile code blocks
  Fix dark mode logo
  Update links
  Implement new website (rome#3556)
@leops leops added the A-Tooling Area: our own build, development, and release tooling label Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Tooling Area: our own build, development, and release tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants