Skip to content

chore(deps): update node docker tag to v26#321

Closed
chrisns wants to merge 2 commits into
mainfrom
renovate/node-26.x
Closed

chore(deps): update node docker tag to v26#321
chrisns wants to merge 2 commits into
mainfrom
renovate/node-26.x

Conversation

@chrisns
Copy link
Copy Markdown
Member

@chrisns chrisns commented May 19, 2026

This PR contains the following updates:

Package Type Update Change
node final major 24.14-alpine26.1-alpine
node stage major 24.14-alpine26.1-alpine
node final major 23-alpine26-alpine

Release Notes

nodejs/node (node)

v26

Moved to doc/changelogs/CHANGELOG_V6.md#6.0.0.

v25

Moved to doc/changelogs/CHANGELOG_V012.md#0.12.8.

v24

Moved to doc/changelogs/CHANGELOG_IOJS.md#2.1.0.


Configuration

📅 Schedule: (in timezone Europe/London)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

…ilures

PR 321 retry uncovered two more issues:

1. delete-file-system fails with ConflictException ("has mount targets")
   on file systems that still have mount targets attached. Add a
   list-mount-targets + delete-mount-target loop before delete-file-system,
   plus a 30s grace for the async deletes to complete.

2. delete_bucket_completely returns 1 when all attempts fail (it opens a
   stranded-stack issue and gives up). The bare function call inside the
   bucket sweep loop is NOT a conditional context, so set -e fires and
   kills the whole pre-deploy script. Adding `|| true` to both the
   bucket-sweep and orphan-stack-sweep loops keeps them tolerant of
   per-item failures; the stranded-stack issues remain the audit trail.

Also captured stderr explicitly (var + echo) for the file-system delete,
matching the pattern used elsewhere — avoids the `cmd | sed` pipefail
trap that killed earlier iterations.
@chrisns chrisns had a problem deploying to smoke-test-deploy May 20, 2026 10:10 — with GitHub Actions Failure
chrisns added a commit that referenced this pull request May 20, 2026
When iterative pre-deploy cleanup has accumulated more debris than the
script can sweep in 90 minutes, manual recovery is needed. Add a
workflow-dispatch workflow + script that runs under the existing
smoke-test-deploy role and clears every:

  - ${STACK}* CloudFormation stack (top-level)
  - AWS::S3Files::FileSystem (with access points + mount targets first)
  - NDXTry_* AppRegistry applications
  - ndx-try-* Connect instances
  - ndx-try-*${ACCOUNT_ID}* S3 buckets

Same identity, same concurrency group as smoke.yml, so the two can't
run simultaneously. Requires typing NUKE as the confirm input to fire,
to avoid accidental destruction of the smoke account.

This is the script side of "manual cleanup" we kept reaching for during
PR #321's CI iterations. After running this, the next smoke run starts
from a true clean slate.
@chrisns chrisns had a problem deploying to smoke-test-deploy May 20, 2026 13:46 — with GitHub Actions Failure
@chrisns chrisns had a problem deploying to smoke-test-deploy May 20, 2026 14:34 — with GitHub Actions Failure
@chrisns chrisns had a problem deploying to smoke-test-deploy May 20, 2026 21:30 — with GitHub Actions Failure
@chrisns chrisns had a problem deploying to smoke-test-deploy May 21, 2026 10:26 — with GitHub Actions Failure
@chrisns
Copy link
Copy Markdown
Member Author

chrisns commented May 22, 2026

Superseded by new renovate grouping (per-scenario + npm-web + github-actions). See #357 for the config change. This PR's dep, if still pending, will be re-opened inside the appropriate grouped PR on the next renovate cycle.

@chrisns chrisns closed this May 22, 2026
@chrisns chrisns deleted the renovate/node-26.x branch May 22, 2026 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant