Update to latest beachball 2.65.3

🧹 Tech Debt

As part of #2947 attempted to update beachball to v2.65.3 however the normal patch had to be reverted in https://github.com/ni/nimble/commit/37dd8c84b5dac80c7a8fbe5b6610cb884b754d18

When addressing this change:

• Fix the patch for the latest beachball
• Re-enable renovate updates for beachball

Failed publish log

> @ni-private/nimble@1.0.0 invoke-publish
> beachball publish --yes --access public --message "applying package updates [skip ci]"


Validating options and change files...

Validating package dependencies...
Skipping bumping private package "@ni-private/angular-workspace"
Skipping bumping private package "@ni-private/site"
Skipping bumping private package "@ni-private/storybook"
Skipping bumping private package "@ni-private/blazor-workspace"
Skipping bumping private package "@ni-private/performance"
Skipping bumping private package "@ni-private/react-client-app"
@ni/unit-format needs to be bumped because @ni/jasmine-parameterized ^1.0.9 -> ^1.0.10
@ni/nimble-components needs to be bumped because @ni/unit-format ^1.0.3 -> ^1.0.4
@ni/nimble-components needs to be bumped because @ni/jasmine-parameterized ^1.0.9 -> ^1.0.10
@ni/spright-components needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/spright-components needs to be bumped because @ni/jasmine-parameterized ^1.0.9 -> ^1.0.10
@ni/ok-components needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/ok-components needs to be bumped because @ni/spright-components ^6.17.1 -> ^6.17.2
@ni/ok-components needs to be bumped because @ni/jasmine-parameterized ^1.0.9 -> ^1.0.10
@ni/nimble-react needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/nimble-react needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/spright-react needs to be bumped because @ni/spright-components ^6.17.1 -> ^6.17.2
@ni/spright-react needs to be bumped because @ni/spright-components ^6.17.1 -> ^6.17.2
@ni/ok-react needs to be bumped because @ni/ok-components ^1.1.1 -> ^1.1.2
@ni/ok-react needs to be bumped because @ni/ok-components ^1.1.1 -> ^1.1.2
@ni/nimble-angular needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/nimble-angular needs to be bumped because @ni/unit-format ^1.0.3 -> ^1.0.4
@ni/spright-angular needs to be bumped because @ni/spright-components ^6.17.1 -> ^6.17.2
@ni/ok-angular needs to be bumped because @ni/ok-components ^1.1.1 -> ^1.1.2
@ni/nimble-blazor needs to be bumped because @ni/nimble-components ^35.7.0 -> ^35.7.1
@ni/spright-blazor needs to be bumped because @ni/spright-components ^6.17.1 -> ^6.17.2
@ni/ok-blazor needs to be bumped because @ni/ok-components ^1.1.1 -> ^1.1.2
Validating no private package among package dependencies
  OK!


Preparing to publish

Publishing with the following configuration:

  registry: https://registry.npmjs.org/

  current branch: main
  current hash: 0b952f1b5ef4f5c52e405d84141fd18b987137d1
  target branch: origin/main
  npm dist-tag: 

  bumps versions before publishing: yes
  publishes to npm registry: yes
  pushes bumps and changelogs to remote git repo: yes


Creating temporary publish branch publish_1777685222183

Bumping versions and publishing packages to npm registry

Updating package-lock.json after bumping packages

up to date, audited 2073 packages in 2s

513 packages are looking for funding
  run `npm fund` for details

6 vulnerabilities (3 low, 3 moderate)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
Using custom renderer for package version changelog.
Removing change files:
- @ni-jasmine-parameterized-b0c877f8-054c-4609-a987-e2311b9fb1b6.json
- @ni-nimble-angular-b5addf24-a469-4e7d-ae6f-fb0c55326cea.json
- @ni-nimble-blazor-da1c37c6-226c-46c0-8aa0-9aced8dfe3c2.json
- @ni-nimble-components-e0204393-a717-4bb4-ab64-1ee36c8d13e7.json
- @ni-ok-angular-cf447d10-e488-43ad-a39d-50858aee71cf.json
- @ni-ok-blazor-d2bdd190-2605-4e50-b8b9-dbd7ca8cc078.json
- @ni-ok-components-30b2a90d-0705-4e55-952a-0e05ae5b01ec.json
- @ni-spright-angular-ff476124-cbee-4896-a900-8057aca5cb88.json
- @ni-spright-blazor-c766ceb3-4adf-4d2a-9c9b-b4fb4addcdef.json
- @ni-spright-components-a9f4d0dd-69de-4a77-9288-710cf8880e30.json
- @ni-unit-format-9fc71be2-99c8-416f-a16f-845b87f6bd47.json
Removing empty change folder
Validating new package versions...

Fetching info about "@ni/jasmine-parameterized" from https://registry.npmjs.org/
Fetching info about "@ni/nimble-angular" from https://registry.npmjs.org/
Fetching info about "@ni/nimble-blazor" from https://registry.npmjs.org/
Fetching info about "@ni/nimble-components" from https://registry.npmjs.org/
Fetching info about "@ni/ok-angular" from https://registry.npmjs.org/
Failed to get or parse npm info for @ni/nimble-blazor: Error: Output:
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@ni%2fnimble-blazor - Not found
npm error 404
npm error 404  The requested resource '@ni/nimble-blazor@*' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://registry.npmjs.org/@ni%2fnimble-blazor - Not found",
    "detail": "The requested resource '@ni/nimble-blazor@*' could not be found or you do not have permission to access it.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-05-02T01_27_04_887Z-debug-0.log
Fetching info about "@ni/ok-blazor" from https://registry.npmjs.org/
Fetching info about "@ni/ok-components" from https://registry.npmjs.org/
Fetching info about "@ni/spright-angular" from https://registry.npmjs.org/
Fetching info about "@ni/spright-blazor" from https://registry.npmjs.org/
Fetching info about "@ni/spright-components" from https://registry.npmjs.org/
Fetching info about "@ni/unit-format" from https://registry.npmjs.org/
Failed to get or parse npm info for @ni/ok-blazor: Error: Output:
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@ni%2fok-blazor - Not found
npm error 404
npm error 404  The requested resource '@ni/ok-blazor@*' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://registry.npmjs.org/@ni%2fok-blazor - Not found",
    "detail": "The requested resource '@ni/ok-blazor@*' could not be found or you do not have permission to access it.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-05-02T01_27_05_463Z-debug-0.log
Fetching info about "@ni/nimble-react" from https://registry.npmjs.org/
Fetching info about "@ni/ok-react" from https://registry.npmjs.org/
Failed to get or parse npm info for @ni/spright-blazor: Error: Output:
Fetching info about "@ni/spright-react" from https://registry.npmjs.org/
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@ni%2fspright-blazor - Not found
npm error 404
npm error 404  The requested resource '@ni/spright-blazor@*' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-05-02T01_27_06_031Z-debug-0.log
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://registry.npmjs.org/@ni%2fspright-blazor - Not found",
    "detail": "The requested resource '@ni/spright-blazor@*' could not be found or you do not have permission to access it.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}
Package versions are OK to publish:
  • @ni/jasmine-parameterized@1.0.10
  • @ni/nimble-angular@33.1.7
  • @ni/nimble-blazor@20.16.4
  • @ni/nimble-components@35.7.1
  • @ni/ok-angular@2.2.2
  • @ni/ok-blazor@1.1.2
  • @ni/ok-components@1.1.2
  • @ni/spright-angular@9.1.3
  • @ni/spright-blazor@4.13.2
  • @ni/spright-components@6.17.2
  • @ni/unit-format@1.0.4
  • @ni/nimble-react@0.14.4
  • @ni/ok-react@0.8.2
  • @ni/spright-react@0.12.3

Validating no private package among package dependencies
  OK!

Publishing - @ni/jasmine-parameterized@1.0.10 with tag latest
  publish command: NaN NaN NaN --registry https://registry.npmjs.org/ --tag latest --loglevel notice --access public
  (cwd: /home/runner/work/nimble/nimble/packages/jasmine-parameterized)

Publishing @ni/jasmine-parameterized@1.0.10 failed. Output:

Unknown command: "NaN"

To see a list of supported npm commands, run:
  npm help

Retrying... (1/3)

Publishing @ni/jasmine-parameterized@1.0.10 failed. Output:
Retrying... (2/3)


Unknown command: "NaN"

To see a list of supported npm commands, run:
  npm help

Publishing @ni/jasmine-parameterized@1.0.10 failed. Output:

Retrying... (3/3)
Unknown command: "NaN"

To see a list of supported npm commands, run:
  npm help


Publishing @ni/jasmine-parameterized@1.0.10 failed. Output:

Unknown command: "NaN"

To see a list of supported npm commands, run:
  npm help

Something went wrong with publishing (see above for details). The following packages were NOT published:
  • @ni/jasmine-parameterized@1.0.10
  • @ni/nimble-angular@33.1.7
  • @ni/nimble-blazor@20.16.4
  • @ni/nimble-components@35.7.1
  • @ni/nimble-react@0.14.4
  • @ni/ok-angular@2.2.2
  • @ni/ok-blazor@1.1.2
  • @ni/ok-components@1.1.2
  • @ni/ok-react@0.8.2
  • @ni/spright-angular@9.1.3
  • @ni/spright-blazor@4.13.2
  • @ni/spright-components@6.17.2
  • @ni/spright-react@0.12.3
  • @ni/unit-format@1.0.4

Unexpected error while running beachball!
Error: Error publishing! Refer to the previous logs for recovery instructions.
    at packagePublishInternal (/home/runner/work/nimble/nimble/node_modules/beachball/lib/publish/publishToRegistry.js:87:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async publishToRegistry (/home/runner/work/nimble/nimble/node_modules/beachball/lib/publish/publishToRegistry.js:93:17)
    at async publish (/home/runner/work/nimble/nimble/node_modules/beachball/lib/commands/publish.js:84:9)
    at async /home/runner/work/nimble/nimble/node_modules/beachball/lib/cli.js:49:13
beachball v2.65.3 - the sunniest version bumping tool
Error: Process completed with exit code 1.

Start by reproducing the beachball v2.65.3 publish failure using the package-lock.json state and the publish command shown in the log. Inspect the beachball publish path identified in node_modules/beachball/lib/publish/publishToRegistry.js and the package publishing setup. Done means publishing completes without the NaN command failure and Renovate updates for beachball are enabled again.