-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bump to 3.7.1 w /dist/ files compiled, yarn.lock removed, updated release workflow issue template #2036
Conversation
Tests failing with:
Ah, interesting:
|
Ah, it's wrong in the package-lock.json file. I'm removing and reinstalling it to get the correct URL format. |
Hmm, this:
Generates this:
and
I guess I'm surprised that although I specify https:// it seems to still by trying to use ssh? |
OK noting an old convo at npm repo about defaulting to |
This seems still open -
|
Aha - it's this: npm/cli#2610 Some are saying it's still not fixed in npm v8.1, so i'm reading the comments for a workaround. |
Huh, ok, so got past the ssh/https issue and now: Expand logs
Looks like an issue with browserify? |
Noting same error in Gitpod when running
|
Odd, could we have changed browsify version while updating package-lock.json? Esp odd as we have updated package-lock.json regularly: https://github.com/publiclab/image-sequencer/commits/main/package-lock.json However we did regenerate it from scratch this time. Let's try reverting and updating just the relevant lines for the https/ssh issue. |
|
Fixes #1751, fixes #2035
Checklist and coordination for v0.0.0 major/minor/patch release
(see semantic versioning)examples/sw.js
(ex Bump lockfile and sw.js versions for v3.6.0 #1734) andpackage.json
(ex Bump to v3.6.0 for new npm release #1695)package.json
npm install
to updatepackage-lock.json
(from recent node version - 16 at time of writing, in GitPod should work)main
branch (freeze merges tomain
branch until next step)Now, move to
stable
branch:main
tostable
stable
branch, compile/dist/
files withgrunt build
/dist/
files withgit add -f /dist/*
and commit them tostable
branchnpm publish
Draft a release:
v0.0.0
) based onstable
or choosestable
npm
withnpm publish
(logging in first as necessary)/scripts/update-demo
) (from within GitPod works well)Noting we're now in this process in #1751 for
v3.7.0
.Release notes
Added
Fixed
v3.7.0
Changed
expr-eval
in switch to expr-eval for dynamic module #1729 by @jywarren