Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update package.json #143

Closed
wants to merge 1 commit into from
Closed

Update package.json #143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@asyncapi/avro-schema-parser",
"version": "1.0.1",
"version": "1.1.0",
"description": "An AsyncAPI schema parser for Avro 1.x schemas.",
"main": "index.js",
"scripts": {
Expand Down Expand Up @@ -30,7 +30,7 @@
},
"homepage": "https://github.com/asyncapi/avro-schema-parser#readme",
"devDependencies": {
"@asyncapi/parser": "^1.14.1",
"@asyncapi/parser": "^1.15.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a dev dependency, so I don't think so that PR is needed. If you only use this dependency for testing then the new changes (in parser core) do not have any breaking changes, so just bumping up the dependencies and the package does not make sense.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes you have absolutely right :) it appears that my holidays was the best effect ^^

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hah no problem, glad you got some rest. Generally this dependency will be bumped automatically, but without releasing the package - our workflow will take care of it :)

"@semantic-release/commit-analyzer": "^8.0.1",
"@semantic-release/github": "^7.0.4",
"@semantic-release/npm": "^7.1.1",
Expand Down