Repository navigation
0.8.4 - #43
Merged
Merged
0.8.4#43
Conversation
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.
0.8.4
Nothing to reinstall — the shell wrapper is unchanged.
gwt sync-envcopiesfewer files than it did, on purpose; the two entries below say which and why.
Fixed
gwt sync-envoverwrote committed.envtemplates. The scan skipped.env.tpl,.env.exampleand their three siblings by exact name, so everyprefixed form went through —
.env.development.tpl,.env.production.tpl,.env.development.example. Those files are usually tracked by git, so the mainworktree's copy landed on top of a branch that had edited one, and
git statusshowed a change nobody made. Run
git add -Aafter that and you commit themain worktree's template into your branch. One monorepo had 44 such files.
The check is on the suffix now, so
.env.<anything>.tplis skipped whateverenvironment it names.
.env.test.localis still copied — it is a localoverride, not a committed fixture.
And a suffix list is only a guess, so git decides. A repository that
versions
.env.defaults— no template suffix anywhere — had the same bug in adifferent shape.
sync-envnow leaves alone any file git tracks in thedestination, whatever it is called, and says how many it left. The suffix rules
stay on top of that, because they carry an intent an index cannot: an untracked
.env.exampleis still an example, and the guard yields nothing when git failsor when a repository has committed nothing yet.
Measured on the monorepo that surfaced this: of 68
.env*files, the 40 gittracks are now left alone and the 28 it does not are still copied — nothing on
the wrong side of either rule.
Internal
actions/checkoutandactions/setup-nodego from v4 to v7, which ends theNode 20 deprecation warning on the runners.
setup-nodev7 also drops thedummy
NODE_AUTH_TOKENexport that maderegistry-urlreturn E401 againstnpm's trusted publisher, so that workaround is no longer load-bearing — it
stays anyway, since the publish path works.
The tracked-file lookup is one
git ls-filesscoped by pathspec. A barelisting measures 1.09 MB on a large monorepo, past
execFileSync's defaultbuffer, against 1.7 KB scoped.
Four worktree colours collide 8.8% of the time, measured over 20,000 draws.
The code said eight percent in one place and one in fourteen in another, and
0.8.3 below says seven; the first was closest. The comments and the test now
carry the measured figure. No colour changes.
After merging
git tag v0.8.4 && git push --tagsCI stages the package; approve it on npmjs.com with 2FA. 165 tests.