Closed aeworxet closed 3 months ago
@asyncapi/bounty_team
@aeworxet If we want to release this, you will need to include a changesets file under .changeset
dir. Check the following message from changeset-bot.
Latest commit: 7968a56519fc07c6c1a1420d2ca8a65c560a7934
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
$ npx changeset
npm ERR! could not determine executable to run
$ npm install npx -g --force
npm WARN using --force Recommended protections disabled.
npm WARN deprecated npx@10.2.2: This package is now part of the npm CLI.
added 1 package in 3s
1 package is looking for funding
run `npm fund` for details
$ npx changeset
npm ERR! cb.apply is not a function
🤷🏻
@ayushnau ?
the command for the cli to create changeset is this npx -p @changesets/cli changeset
@aeworxet
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Should command npx -p @changesets/cli changeset
be written in a README somewhere? I wouldn't know it if @ayushnau didn't tell.
$ grep -iHr changesets/cli .
./node_modules/eslint-plugin-prettier/package.json: "@changesets/cli": "^2.27.1",
./.github/workflows/release-with-changesets.yml: version: npx -p @changesets/cli changeset version
./.github/workflows/release-with-changesets.yml: publish: npx -p @changesets/cli changeset publish
Click here if you're a maintainer who wants to add another changeset to this PR
Sure, feel free to add it. cc @ayushnau BTW, you have a link in https://github.com/asyncapi/parser-js/pull/1042#issuecomment-2250005327 that redirects you to create the file.
https://github.com/asyncapi/parser-js/pull/1042#issuecomment-2250005327 redirects to
Run
npx changeset
oryarn changeset
while @ayushnau pointed to
npx -p @changesets/cli changeset
That's why I thought this matter needed clarification. :shrug:
Anyway, I've already added the changeset because I need to specify a new version of @asyncapi/parser
in PR for both Studio
s; can this PR be merged?
https://github.com/asyncapi/parser-js/pull/1042#issuecomment-2250005327 redirects to
Run
npx changeset
oryarn changeset
while @ayushnau pointed to
npx -p @changesets/cli changeset
That's why I thought this matter needed clarification. :shrug:
Anyway, I've already added the changeset because I need to specify a new version of
@asyncapi/parser
in PR for bothStudio
s; can this PR be merged?
The last link of such comment redirects you right directly to the changeset file creation: https://github.com/aeworxet/asyncapi-parser-js/new/chore-deps-bump-ajv-to-8.17.1?filename=.changeset/mean-mice-buy.md&value=---%0A%22%40asyncapi%2Fparser%22%3A%20patch%0A---%0A%0Achore(deps)%3A%20bump%20ajv%20to%208.17.1%0A Next time you can use it.
/rtm
This PR upgrades
ajv
to version8.17.1
to lay the foundation for fixing https://github.com/asyncapi/parser-js/issues/980.Related to https://github.com/asyncapi/parser-js/issues/1012