Repository navigation
release: v1.9.4 - #4320
Merged
Merged
release: v1.9.4#4320
Conversation
Member
Contributor
CodSpeed Performance ReportMerging #4320 will not alter performanceComparing Summary
|
Conaclos
force-pushed
the
release/1.9.4
branch
from
October 17, 2024 15:33
03923da to
9d71150
Compare
Member
Author
You are right. I reverted the change in the PR. I think we can merge it today :) |
Contributor
Parser conformance results onjs/262
🎉 Fixed (16):jsx/babel
symbols/microsoft
ts/babel
ts/microsoft
🔥 Regression (2):🎉 Fixed (1): |
ematipico
approved these changes
Oct 17, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a changelog entry for every Pull Request that lacks one.
You can filter merged PRs that don't update the changelog.
Read our guidelines for editing the changelog.
Based on the changelog, determine which version number to use.
See our versioning guide for more details.
Rename
Unreleasedto<version> (iso-date)in the changelog.Update
versionin Biome'spackage.jsonif applicable.Update to the sameversionin all crates if you publish crates. (Cargo.tomlandcrates/**/Cargo.toml)Linter rules have a
versionmetadata directly defined in their implementation.This field is set to
nextfor newly created rules.This field must be updated to the new version.
Update the website with the new version number:
BIOME_VERSION=<version> just gen-web.This will also copy the configuration schema in the right place.
Once the PR is merged, the CI will trigger the
Release: *workflows. Once these workflows finish compiling the final artefact, they need to be approved manually.