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.

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

ci: change dependency to devDependency #241

Merged
merged 1 commit into from
May 24, 2023

Conversation

Shurtu-gal
Copy link
Contributor

Description
Convert conventional-changelog-conventionalcommits to devDependency.

Related issue(s)
Fixes #237

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@derberg derberg changed the title fix: change dependency to devDependency ci: change dependency to devDependency May 24, 2023
Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

Thanks!

@derberg
Copy link
Member

derberg commented May 24, 2023

/rtm

@Shurtu-gal if you want another more challenging task, I recommend #242, feel free to ask for help if needed

@asyncapi-bot asyncapi-bot merged commit 31b1ebe into asyncapi:master May 24, 2023
@Shurtu-gal
Copy link
Contributor Author

/rtm

@Shurtu-gal if you want another more challenging task, I recommend #242, feel free to ask for help if needed

It's already taken up. I guess I will continue with auto update issue of vranches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

I think there is a potential bug in release pipeline
3 participants