Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prepare semver (
@latest
) releases in CI
Now that we track package versions in source, `@latest` builds should be fully reproducible for a given commit. We can prepare the packages in CI and store them as artifacts, the same way we do for `@next` and `@experimental`. Eventually this can replace the interactive script that we currently use to swap out the version numbers. The other nice thing about this approach is that we can run tests in CI to verify that the packages are releasable, instead of waiting until right before publish. I named the output directory `oss-stable-semver`, to distinguish from the `@next` prereleases that are located at `oss-stable`. I don't love this naming. I'd prefer to use the name of the corresponding npm dist tag. I'll do that in a follow-up, though, since the `oss-stable` name is referenced in a handful of places. Current naming (after this PR): - `oss-experimental` → `@experimental` - `oss-stable` → `@next` - `oss-stable-semver` → `@latest` Proposed naming (not yet implemented, requires more work): - `oss-experimental` → `@experimental` - `oss-next` → `@next` - `oss-latest` → `@latest`
- Loading branch information