This repository has been archived by the owner on Dec 9, 2022. It is now read-only.
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.
This PR contains the following updates:
0.7.1
->0.9.1
Release Notes
google/wireit
v0.9.1
Compare Source
Added
env
setting which allows either directly assigning environmentvariables, or indicating that an externally-provided environment variable
should affect the fingerprint (and hence freshness/caching). Example:
v0.9.0
Compare Source
Changed
[BREAKING] A
watch
argument (without the--
) is now passed to thescript, instead of erroring, to make it consistent with all other arguments.
(The error was previously repoted to aid in migration from
watch
to--watch
, which changed in `v0.6.0).[BREAKING] The
.yarn/
folder has been added to the list of defaultexcluded paths.
It is now allowed to set the value of a wireit script to e.g.
"../node_modules/.bin/wireit"
if you need to directly reference a wireitbinary in a specific location.
yarn.lock
andpnpm-lock.yaml
are now automatically used as package lockfiles when yarn and pnpm are detected, respectively. (Previously
package-lock.json
was always used unless thepackageLocks
array wasmanually set).
Fixed
--watch
flag can now be passed to chained scripts when using yarn 1.x.However duehttps://github.com/yarnpkg/yarn/issues/89058905, extra arguments
passed after a
--
are still not supported with yarn 1.x. Please considerupgrading to yarn 3.x, or switching to npm.
v0.8.0
Compare Source
Added
[BREAKING] The following folders are now excluded by default from both the
files
andoutput
arrays:.git/
.hg/
.svn/
.wireit/
CVS/
node_modules/
In the highly unusual case that you need to reference a file in one of those
folders, set
allowUsuallyExcludedPaths: true
to remove all default excludes.Fixed
Fixed
Invalid string length
andheap out of memory
errors when writing thefingerprint files for large script graphs.
Fixed bug where an exclude pattern for a folder with a trailing slash would
not be applied (e.g.
!foo
worked but!foo/
did not).v0.7.3
Compare Source
Added
Added
"service": true
setting, which is well suited for long-runningprocesses like servers. A service is started either when it is invoked directly,
or when another script that depends on it is ready to run. A service is stopped
when all scripts that depend on it have finished, or when Wireit is exited.
Added
"cascade": false
setting to dependencies.By default, the fingerprint of a script includes the fingerprints of its
dependencies. This means a script will re-run whenever one of its dependencies
re-runs, even if the output produced by the dependency didn't actually change.
Now, if a dependency is annotated with
"cascade": false
, then thefingerprint of that dependency will no longer be included in the script's own
fingerprint. This means a script won't neccessarily re-run just because a
dependency re-ran — though Wireit will still always run the dependency first
if it is not up-to-date.
Using
"cascade": false
can result in faster builds thanks to fewer re-runs,but it is very important to specify all of the input files generated by the
dependency which the script depends on in the
files
array.Example:
Changed
command
,dependencies
,files
,output
, andpackageLocks
properties inschema.json
.Fixed
Fixed memory leak in watch mode.
Added graceful recovery from
ECONNRESET
and other connection errors whenusing GitHub Actions caching.
Fixed bug where a leading slash on a
files
oroutput
path was incorrectlyinterpreted as relative to the filesystem root, instead of relative to the
package, in watch mode.
v0.7.2
Compare Source
Fixed
multiple scripts were watching the same file(s).
Changed
stdout color output is now forced when Wireit is run with a text terminal
attached.
Default number of scripts run in parallel is now 2x logical CPU cores instead
of 4x.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.