chore(release): v1.8.9-alpha prep — What's New block + version bumps
Demo images / Build & push demo images (push) Successful in 3m48s
Demo images / Build & push demo images (push) Successful in 3m48s
The release gate requires the freshly-built bundle to embed the new version, and the version reaches the bundle through the What's New modal in AccountInfoSection — there was no v1.8.9-alpha block yet, so create-release.sh correctly refused to ship a bundle that looked stale. This adds the block (the user-facing summary of today's LND/HTTPS/ launcher/NPM/Portainer fixes) and carries the version bumps the aborted run had already written (Cargo.toml, Cargo.lock, package.json, package-lock), so the re-run starts from a clean tree. Verified: npm run build now produces assets containing 1.8.9-alpha (Settings chunk), i.e. the exact check the script runs passes.
This commit is contained in:
Generated
+2
-2
@@ -1,12 +1,12 @@
|
||||
{
|
||||
"name": "neode-ui",
|
||||
"version": "1.8.8-alpha",
|
||||
"version": "1.8.9-alpha",
|
||||
"lockfileVersion": 3,
|
||||
"requires": true,
|
||||
"packages": {
|
||||
"": {
|
||||
"name": "neode-ui",
|
||||
"version": "1.8.8-alpha",
|
||||
"version": "1.8.9-alpha",
|
||||
"dependencies": {
|
||||
"@scure/bip39": "^2.2.0",
|
||||
"@types/dompurify": "^3.0.5",
|
||||
|
||||
Reference in New Issue
Block a user