Prepares the 9.4.2 release (HELD for the operator) - #229
Merged
Merged
Conversation
`@version` moves to 9.4.2 and the two open `changelog.d/` fragments are assembled into a dated 9.4.2 section at the top of `CHANGELOG.md`, then deleted. Both are `### Fixed` entries and both are promoted byte for byte: the uppercase `\U` escape refusal and the non-ASCII date-literal error message. Nothing else on main since v9.4.1 earns a bullet - the language-reference pass carried no behaviour change, and the library corpus rows are conformance fixtures, which `changelog.d/README.md` lists first under "Do not write a fragment for". A patch bump, so the README install pin does not move. The release recipe says of it: "It moves only on a major/minor bump - a patch release leaves it alone, so the two carriers agree on major and minor and say nothing about patch." The pin already reads the current major and minor. No tag is created here. The tag, the push and the publish are the operator's. Refs: px-svb
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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.
What this is
The 9.4.2 release prep, opened last in this repository and HELD for the
operator. The merge, the tag and the publish are the operator's; this pull
request exists to be read and then acted on by them. No tag was created,
locally or on the remote.
Why this release exists
A sibling package vendors this repository's conformance corpus from a tag,
and the library world's guards landed on
mainas corpus rows after v9.4.1was cut. There is no tag carrying them. This release cuts one, and picks up
the two unreleased lexer fixes that were waiting on it.
What moved
Four files, and only the release carriers:
mix.exs-@version9.4.1 -> 9.4.2.CHANGELOG.md- a new dated## [9.4.2]section at the top.changelog.d/px-2ms.md- deleted, promoted into that section.changelog.d/px-h7p.md- deleted, promoted into that section.The version is an honest patch
git log v9.4.1..HEADat the base of this branch enumerates four commits:6dd1758- fixes non-ASCII truncation in date literals (take_date/5).d06ece1- documents string escapes and the numeric refusal; docs only.71ae4da- refuses an uppercase\Uescape like\u(take_string/6).f2f982d- adds the library world's guards as corpus rows.Two bug fixes, one documentation pass, one conformance-fixture addition. No
public function is added, removed or changed, and no observable behaviour
changes except the two refusals/messages the fixes name. A patch bump is what
SemVer gives for that set.
The 9.4.2 section
Both fragments carry
### Fixedand both are promoted byte for byte, with noparaphrase and nothing added:
\Uescape in a string literal is refused with the same error as\u.Each is true against 9.4.1 as released. 9.4.1's own
### Fixedblocknames the lowercase
\urefusal and non-ASCII string literals; neither ofthese two bullets restates it. The uppercase spelling was still falling
through after 9.4.1 shipped, and the date-literal message was still being
truncated.
The README install pin is unchanged, on purpose
9.4.1 -> 9.4.2 is a patch. The release recipe says of the pin, verbatim:
The pin already reads the current major and minor, so an unchanged pin here
is the recipe being followed, not a missed step.
No fragment for the library corpus rows
changelog.d/README.md's "Do not write a fragment for" list opens with "testharness, corpus tooling, or conformance fixtures", with no exception. The
library world's guards are conformance fixtures, so they take no fragment and
no bullet. The 9.4.2 section is assembled from the two fragments already open
on
mainand nothing else.Gate
Full
mix qualitygreen at the head of this branch, attested:Doctor is a standing project-level gap (
:doctor not installed), skipped onevery run here and not a passing stage.
mix hex.buildSucceeds at 9.4.2. Its file list:
The built tarball was deleted after the file list was read; it is not in the
tree and not in this branch.
ISA and corpus
Neither moves here. This branch touches no file under
conformance/, notdocs/isa.md, and notlib/predicator/instructions.ex. The corpus rows thisrelease carries landed separately and are already on
main.Provenance
No edit outside the four release carriers was needed, so nothing is listed
here beyond them.
For the operator
Merge (rebase), then tag and publish. Nothing in this branch does any of
those.