[BUG]: `VERSION` placeholder is not replaced in bundled dist

[wxh06]

What happened?

We can clearly see that, in each version starting from 9.0.0-beta.1, the VERSION constant in dist-bundle/index.js has always been set to the placeholder value 0.0.0-development, which is supposed to be replaced by semantic-release-plugin-update-version-in-files with the actual version number.

As a result, the default User-Agent does not have the correct version number for octokit-request.js either.

> require("@octokit/request").request.endpoint.DEFAULTS;
{
  method: 'GET',
  baseUrl: 'https://api.github.com',
  headers: {
    accept: 'application/vnd.github.v3+json',
    'user-agent': 'octokit-request.js/0.0.0-development Node.js/20.19.2 (darwin; arm64)'
  },
  mediaType: { format: '' }
}

It was introduced in #678

Expected

var VERSION = "10.0.2";

Actual

var VERSION = "0.0.0-development";

Versions

@octokit/request@>=9.0.0-beta.1

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[octokit]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[wolfy1339]

Do you mind submitting a PR for this? It's a pretty simple trivial fix.

request.js/package.json

Lines 71 to 75 in fe8bb4b

	"files": [
	"pkg/dist-web/*",
	"pkg/dist-node/*",
	"pkg/*/version.*"
	]

This might not be the only case in the Octokit packages, as I made the same change in other repositories as well

[github-actions]

🎉 This issue has been resolved in version 10.0.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[wxh06]

Do you mind submitting a PR for this? It's a pretty simple trivial fix.

When I intended to submit a PR earlier, it prompted me that I had to first create an issue for it :)

[wolfy1339]

For trivial fixes like these you can safely skip issues.

It's mainly meant for bigger changes, like introducing new features, and refactoring the code base.