Bump skuba from 13.1.1 to 14.1.0

[dependabot]

Bumps skuba from 13.1.1 to 14.1.0.

Release notes

Sourced from skuba's releases.

skuba@14.1.0

Minor Changes

• lint: Add rootDir: './src' to tsconfig.build.json files (#2217)

Patch Changes

• deps: prettier ~3.8.0 (#2213)

• deps: ejs ^4.0.0 (#2215)

• deps: zod ^4.3.5 (#2218)

  This resolves errors such as "ID X already exists in the registry" caused by multiple Zod versions.

  If your package declares a dependency on Zod, ensure you use unpinned versioning (e.g. "zod": "^4.3.5" instead of "zod": "4.3.5") to avoid installing multiple versions.

skuba@14.0.1

Patch Changes

• test: Revert upgrade skuba in CI environments (#2208)

skuba@14.0.0

Major Changes

• migrate: Introduce skuba migrate node24 (#2165)

  skuba migrate node24 attempts to automatically upgrade your:

  • Project to Node.js 24
  • Package targets to Node.js 22.14.0+
  • aws-cdk-lib, datadog-cdk-constructs-v2, osls, serverless, serverless-plugin-datadog, and @types/node dependencies to versions that support Node.js 24

  Changes must be manually reviewed by an engineer before committing the migration output. If you have an npm package that previously supported Node.js ≤18 and was upgraded to target Node.js 22.14.0+, follow semantic versioning and publish the change as a new major version. See skuba migrate node for more information on this feature and how to use it responsibly.

  skuba may not be able to upgrade all projects. Check your project for files that may have been missed, review and test the modified code as appropriate before releasing to production, and open an issue if your project files were corrupted by the migration.

  Node.js 24 includes breaking changes. For more information on the upgrade, refer to:

  • The Node.js release notes
  • The AWS release announcement for the Lambda nodejs24.x runtime update

• deps: Require Node.js 22.14.0+ (#2165)

• format, lint: Migrate projects to Node.js 24 and package targets to Node.js 22.14+ (#2165)

  You can locally opt out of the migration by setting the SKIP_NODE_UPGRADE environment variable, running skuba format, and committing the result.

  Changes must be manually reviewed by an engineer before merging the migration output. If you have an npm package that previously supported Node.js ≤18 and was upgraded to target Node.js 22.14.0+, follow semantic versioning and publish the change as a new major version. See skuba migrate node for more information on this feature and how to use it responsibly.

... (truncated)

Changelog

Sourced from skuba's changelog.

14.1.0

Minor Changes

• lint: Add rootDir: './src' to tsconfig.build.json files (#2217)

Patch Changes

• deps: prettier ~3.8.0 (#2213)

• deps: ejs ^4.0.0 (#2215)

• deps: zod ^4.3.5 (#2218)

  This resolves errors such as "ID X already exists in the registry" caused by multiple Zod versions.

  If your package declares a dependency on Zod, ensure you use unpinned versioning (e.g. "zod": "^4.3.5" instead of "zod": "4.3.5") to avoid installing multiple versions.

14.0.1

Patch Changes

• test: Revert upgrade skuba in CI environments (#2208)

14.0.0

Major Changes

• migrate: Introduce skuba migrate node24 (#2165)

  skuba migrate node24 attempts to automatically upgrade your:

  • Project to Node.js 24
  • Package targets to Node.js 22.14.0+
  • aws-cdk-lib, datadog-cdk-constructs-v2, osls, serverless, serverless-plugin-datadog, and @types/node dependencies to versions that support Node.js 24

  Changes must be manually reviewed by an engineer before committing the migration output. If you have an npm package that previously supported Node.js ≤18 and was upgraded to target Node.js 22.14.0+, follow semantic versioning and publish the change as a new major version. See skuba migrate node for more information on this feature and how to use it responsibly.

  skuba may not be able to upgrade all projects. Check your project for files that may have been missed, review and test the modified code as appropriate before releasing to production, and open an issue if your project files were corrupted by the migration.

  Node.js 24 includes breaking changes. For more information on the upgrade, refer to:

  • The Node.js release notes
  • The AWS release announcement for the Lambda nodejs24.x runtime update

• deps: Require Node.js 22.14.0+ (#2165)

• format, lint: Migrate projects to Node.js 24 and package targets to Node.js 22.14+ (#2165)

  You can locally opt out of the migration by setting the SKIP_NODE_UPGRADE environment variable, running skuba format, and committing the result.

  Changes must be manually reviewed by an engineer before merging the migration output. If you have an npm package that previously supported Node.js ≤18 and was upgraded to target Node.js 22.14.0+, follow semantic versioning and publish the change as a new major version. See skuba migrate node for more information on this feature and how to use it responsibly.

... (truncated)

Commits

• 37f6453 Version Packages (#2216)
• ff8310b Declare explicit dependency on Zod + Bump Zod (#2218)
• 5517011 template: dependency datadog lambda extension layer to v92 (#2212)
• c91be01 deps: ejs ^4.0.0 (#2215)
• be4f5ad Add rootDir to tsconfig.build.json compilerOptions (#2217)
• 1674bd1 template: @​opentelemetry/instrumentation-aws-sdk ^0.65.0 (#2214)
• cc762fb deps: prettier ~3.8.0 (#2213)
• 359f5ad template: opentelemetry (#2202)
• b4a39e7 Version Packages (#2211)
• 626450c Fix skuba-dive build (#2210)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.