Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement โ†’
Sign In

@asyncapi/java-spring-cloud-stream-template

Package Overview
Dependencies
Maintainers
3
Versions
42
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@asyncapi/java-spring-cloud-stream-template - npm Package Compare versions

Comparing version
0.12.1
to
0.13.0
+36
.github/workflows/link-check-cron.yml
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
name: Check Markdown links (Weekly)
on:
workflow_dispatch:
schedule:
# At 00:00 UTC on every Monday
- cron: '0 0 * * 0'
jobs:
External-link-validation-weekly:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
# Checks the status of hyperlinks in .md files
- name: Check links
uses: gaurav-nelson/github-action-markdown-link-check@v1
with:
use-quiet-mode: 'yes'
use-verbose-mode: 'yes'
# A configuration file can be included, indicating the properties of the link check action
# More information can be found here: https://github.com/tcort/markdown-link-check#config-file-format
# Create mlc_config.json file in the root of the directory
- name: Report workflow run status to Slack
uses: 8398a7/action-slack@v3
with:
status: ${{ job.status }}
fields: repo,action,workflow
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}
if: failure() # Only, on failure, send a message on the Slack Docs Channel (if there are broken links)
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
name: Check Markdown links
on:
pull_request_target:
types: [synchronize, ready_for_review, opened, reopened]
paths:
- '**.md'
jobs:
External-link-validation-on-PR:
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v3
- name: Check links
uses: gaurav-nelson/github-action-markdown-link-check@v1
with:
use-quiet-mode: 'yes'
use-verbose-mode: 'yes'
check-modified-files-only: 'yes' # Only modified files are checked on PRs
# A configuration file can be included, indicating the properties of the link check action
# More information can be found here: https://github.com/tcort/markdown-link-check#config-file-format
# Create mlc_config.json file in the root of the directory
# Contributing to AsyncAPI
We love your input! We want to make contributing to this project as easy and transparent as possible.
## Contribution recogniton
We use [All Contributors](https://allcontributors.org/docs/en/specification) specification to handle recognitions. For more details read [this](https://github.com/asyncapi/community/blob/master/recognize-contributors.md) document.
## Summary of the contribution flow
The following is a summary of the ideal contribution flow. Please, note that Pull Requests can also be rejected by the maintainers when appropriate.
```
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ โ”‚
โ”‚ Open an issue โ”‚
โ”‚ (a bug report or a โ”‚
โ”‚ feature request) โ”‚
โ”‚ โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
โ‡ฉ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ โ”‚
โ”‚ Open a Pull Request โ”‚
โ”‚ (only after issue โ”‚
โ”‚ is approved) โ”‚
โ”‚ โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
โ‡ฉ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ โ”‚
โ”‚ Your changes will โ”‚
โ”‚ be merged and โ”‚
โ”‚ published on the next โ”‚
โ”‚ release โ”‚
โ”‚ โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
```
## Code of Conduct
AsyncAPI has adopted a Code of Conduct that we expect project participants to adhere to. Please [read the full text](./CODE_OF_CONDUCT.md) so that you can understand what sort of behaviour is expected.
## Our Development Process
We use Github to host code, to track issues and feature requests, as well as accept pull requests.
## Issues
[Open an issue](https://github.com/asyncapi/asyncapi/issues/new) **only** if you want to report a bug or a feature. Don't open issues for questions or support, instead join our [Slack workspace](https://www.asyncapi.com/slack-invite) and ask there. Don't forget to follow our [Slack Etiquette](https://github.com/asyncapi/community/blob/master/slack-etiquette.md) while interacting with community members! It's more likely you'll get help, and much faster!
## Bug Reports and Feature Requests
Please use our issues templates that provide you with hints on what information we need from you to help you out.
## Pull Requests
**Please, make sure you open an issue before starting with a Pull Request, unless it's a typo or a really obvious error.** Pull requests are the best way to propose changes to the specification. Get familiar with our document that explains [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) used in our repositories.
## Conventional commits
Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
- `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
- `feat: ` prefix in the title indicates that PR is a feature and MINOR release must be triggered.
- `docs: ` prefix in the title indicates that PR is only related to the documentation and there is no need to trigger release.
- `chore: ` prefix in the title indicates that PR is only related to cleanup in the project and there is no need to trigger release.
- `test: ` prefix in the title indicates that PR is only related to tests and there is no need to trigger release.
- `refactor: ` prefix in the title indicates that PR is only related to refactoring and there is no need to trigger release.
What about MAJOR release? just add `!` to the prefix, like `fix!: ` or `refactor!: `
Prefix that follows specification is not enough though. Remember that the title must be clear and descriptive with usage of [imperative mood](https://chris.beams.io/posts/git-commit/#imperative).
Happy contributing :heart:
## License
When you submit changes, your submissions are understood to be under the same [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE) that covers the project. Feel free to [contact the maintainers](https://www.asyncapi.com/slack-invite) if that's a concern.
## References
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).
+3
-3

@@ -1,5 +0,5 @@

#This workflow is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#Purpose of this workflow is to enable anyone to label issue with 'Good First Issue' and 'area/*' with a single command.
# Purpose of this workflow is to enable anyone to label issue with 'Good First Issue' and 'area/*' with a single command.
name: Add 'Good First Issue' and 'area/*' labels # if proper comment added

@@ -6,0 +6,0 @@

@@ -1,7 +0,10 @@

#This workflow is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#Purpose of this workflow is to enable anyone to label PR with `ready-to-merge` and `do-not-merge` labels to get stuff merged or blocked from merging
name: Add ready-to-merge or do-not-merge label # if proper comment added
# Purpose of this workflow is to enable anyone to label PR with the following labels:
# `ready-to-merge` and `do-not-merge` labels to get stuff merged or blocked from merging
# `autoupdate` to keep a branch up-to-date with the target branch
name: Label PRs # if proper comment added
on:

@@ -13,17 +16,66 @@ issue_comment:

jobs:
parse-comment-and-add-ready: # for handling cases when you want to mark as ready to merge
if: github.event.issue.pull_request && github.event.issue.state != 'closed' && github.actor != 'asyncapi-bot'
add-ready-to-merge-label:
if: >
github.event.issue.pull_request &&
github.event.issue.state != 'closed' &&
github.actor != 'asyncapi-bot' &&
(
contains(github.event.comment.body, '/ready-to-merge') ||
contains(github.event.comment.body, '/rtm' )
)
runs-on: ubuntu-latest
steps:
- name: Check if PR is draft # such info is not available in the context of issue_comment event
- name: Add ready-to-merge label
uses: actions/github-script@v5
id: checkDraft
with:
result-encoding: string
github-token: ${{ secrets.GH_TOKEN }}
script: |
const prDetailsUrl = context.payload.issue.pull_request.url;
const response = await github.request(prDetailsUrl);
return response.data.draft;
- name: Add label
if: steps.checkDraft.outputs.result == 'false' && (contains(github.event.comment.body, '/ready-to-merge') || contains(github.event.comment.body, '/rtm' ))
const { data: pull } = await github.request(prDetailsUrl);
const { draft: isDraft} = pull;
if(!isDraft) {
console.log('adding ready-to-merge label...');
github.rest.issues.addLabels({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
labels: ['ready-to-merge']
})
}
const { data: comparison } =
await github.rest.repos.compareCommitsWithBasehead({
owner: pull.head.repo.owner.login,
repo: pull.head.repo.name,
basehead: `${pull.base.label}...${pull.head.label}`,
});
if (comparison.behind_by !== 0 && pull.mergeable_state === 'behind') {
console.log(`This branch is behind the target by ${comparison.behind_by} commits`)
console.log('adding out-of-date comment...');
github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: `Hello, @${{ github.actor }}! ๐Ÿ‘‹๐Ÿผ
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: Add a comment to your PR with the text: \`/au\` or \`/autoupdate\` and our bot will take care of updating the branch in the future. The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR.
Thanks ๐Ÿ˜„`
})
}
add-do-not-merge-label:
if: >
github.event.issue.pull_request &&
github.event.issue.state != 'closed' &&
github.actor != 'asyncapi-bot' &&
(
contains(github.event.comment.body, '/do-not-merge') ||
contains(github.event.comment.body, '/dnm' )
)
runs-on: ubuntu-latest
steps:
- name: Add do-not-merge label
uses: actions/github-script@v5

@@ -37,11 +89,16 @@ with:

repo: context.repo.repo,
labels: ['ready-to-merge']
labels: ['do-not-merge']
})
parse-comment-and-add-block: # for handling cases when you want to mark as do-not-merge
if: github.event.issue.pull_request && github.event.issue.state != 'closed' && github.actor != 'asyncapi-bot'
add-autoupdate-label:
if: >
github.event.issue.pull_request &&
github.event.issue.state != 'closed' &&
github.actor != 'asyncapi-bot' &&
(
contains(github.event.comment.body, '/autoupdate') ||
contains(github.event.comment.body, '/au' )
)
runs-on: ubuntu-latest
steps:
- name: Add label
if: contains(github.event.comment.body, '/do-not-merge') || contains(github.event.comment.body, '/dnm' )
- name: Add autoupdate label
uses: actions/github-script@v5

@@ -55,3 +112,3 @@ with:

repo: context.repo.repo,
labels: ['do-not-merge']
})
labels: ['autoupdate']
})

@@ -1,5 +0,5 @@

#This workflow is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#Purpose of this workflow is to allow people to merge PR without a need of maintainer doing it. If all checks are in place (including maintainers approval) - JUST MERGE IT!
# Purpose of this workflow is to allow people to merge PR without a need of maintainer doing it. If all checks are in place (including maintainers approval) - JUST MERGE IT!
name: Automerge For Humans

@@ -6,0 +6,0 @@

@@ -1,3 +0,3 @@

#This workflow is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -4,0 +4,0 @@ # Defence from evil contributor that after adding `ready-to-merge` all suddenly makes evil commit or evil change in PR title

@@ -1,3 +0,3 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -60,5 +60,5 @@ name: 'Notify on failing automerge'

env:
SLACK_WEBHOOK: ${{secrets.SLACK_GITHUB_NEWISSUEPR}}
SLACK_WEBHOOK: ${{secrets.SLACK_CI_FAIL_NOTIFY}}
SLACK_TITLE: ๐Ÿšจ Not merged PR that should be automerged ๐Ÿšจ
SLACK_MESSAGE: ${{steps.issuemarkdown.outputs.text}}
MSG_MINIMAL: true

@@ -13,3 +13,4 @@ # This action is centrally managed in https://github.com/asyncapi/.github/

jobs:
autoapprove:
autoapprove-for-bot:
name: Autoapprove PR comming from a bot
if: >

@@ -24,3 +25,3 @@ contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]"]'), github.event.pull_request.user.login) &&

with:
github-token: "${{ secrets.GITHUB_TOKEN }}"
github-token: "${{ secrets.GH_TOKEN_BOT_EVE }}"

@@ -36,7 +37,8 @@ - name: Label autoapproved

repo: context.repo.repo,
labels: ['autoapproved']
labels: ['autoapproved', 'autoupdate']
})
automerge:
needs: [autoapprove]
automerge-for-bot:
name: Automerge PR autoapproved by a bot
needs: [autoapprove-for-bot]
runs-on: ubuntu-latest

@@ -43,0 +45,0 @@ steps:

@@ -1,5 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#This workflow is designed to work with:
# This workflow is designed to work with:
# - autoapprove and automerge workflows for dependabot and asyncapibot.

@@ -9,3 +9,3 @@ # - special release branches that we from time to time create in upstream repos. If we open up PRs for them from the very beginning of the release, the release branch will constantly update with new things from the destination branch they are opened against

# It uses GitHub Action that auto-updates pull requests branches, whenever changes are pushed to their destination branch.
#Autoupdating to latest destination branch works only in the context of upstream repo and not forks
# Autoupdating to latest destination branch works only in the context of upstream repo and not forks

@@ -23,3 +23,4 @@ name: autoupdate

jobs:
autoupdate:
autoupdate-for-bot:
name: Autoupdate autoapproved PR created in the upstream
runs-on: ubuntu-latest

@@ -30,6 +31,6 @@ steps:

env:
GITHUB_TOKEN: '${{ secrets.GH_TOKEN }}'
GITHUB_TOKEN: '${{ secrets.GH_TOKEN_BOT_EVE }}'
PR_FILTER: "labelled"
PR_LABELS: "autoapproved"
PR_LABELS: "autoupdate"
PR_READY_STATE: "ready_for_review"
MERGE_CONFLICT_ACTION: "ignore"

@@ -1,6 +0,6 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#Purpose of this action is to update npm package in libraries that use it. It is like dependabot for asyncapi npm modules only.
#It runs in a repo after merge of release commit and searches for other packages that use released package. Every found package gets updated with lates version
# Purpose of this action is to update npm package in libraries that use it. It is like dependabot for asyncapi npm modules only.
# It runs in a repo after merge of release commit and searches for other packages that use released package. Every found package gets updated with lates version

@@ -10,4 +10,4 @@ name: Bump package version in dependent repos - if Node project

on:
#It cannot run on release event as when release is created then version is not yet bumped in package.json
#This means we cannot extract easily latest version and have a risk that package is not yet on npm
# It cannot run on release event as when release is created then version is not yet bumped in package.json
# This means we cannot extract easily latest version and have a risk that package is not yet on npm
push:

@@ -18,3 +18,4 @@ branches:

jobs:
bump:
bump-in-dependent-projects:
name: Bump this package in repositories that depend on it
if: startsWith(github.event.commits[0].message, 'chore(release):')

@@ -35,2 +36,2 @@ runs-on: ubuntu-latest

committer_email: info@asyncapi.io
repos_to_ignore: html-template #this is temporary until react component releases 1.0, then it can be removed
repos_to_ignore: html-template # this is temporary until react component releases 1.0, then it can be removed

@@ -1,3 +0,3 @@

#This workflow is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This workflow is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -28,2 +28,3 @@ name: Create help comment

- `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
- `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict.
create_help_comment_issue:

@@ -30,0 +31,0 @@ if: ${{ !github.event.issue.pull_request && contains(github.event.comment.body, '/help') && github.actor != 'asyncapi-bot' }}

@@ -1,4 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#It does magic only if there is go.mod file in the root of the project
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# It does magic only if there is go.mod file in the root of the project
name: PR testing - if Go project

@@ -11,4 +12,4 @@

jobs:
lint:
name: lint
lint-go-pr:
name: Lint Go PR
runs-on: ubuntu-latest

@@ -39,4 +40,4 @@ steps:

test:
name: ${{ matrix.os }}
test-go-pr:
name: Test Go PR - ${{ matrix.os }}
runs-on: ${{ matrix.os }}

@@ -43,0 +44,0 @@ strategy:

@@ -1,4 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#It does magic only if there is package.json file in the root of the project
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# It does magic only if there is package.json file in the root of the project
name: PR testing - if Node project

@@ -11,4 +12,4 @@

jobs:
test:
name: ${{ matrix.os }}
test-nodejs-pr:
name: Test NodeJS PR - ${{ matrix.os }}
runs-on: ${{ matrix.os }}

@@ -15,0 +16,0 @@ strategy:

@@ -1,4 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#It does magic only if there is package.json file in the root of the project
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# It does magic only if there is package.json file in the root of the project
name: Release - if Node project

@@ -20,4 +21,4 @@

test:
name: Test on ${{ matrix.os }}
test-nodejs:
name: Test NodeJS release on ${{ matrix.os }}
runs-on: ${{ matrix.os }}

@@ -53,3 +54,3 @@ strategy:

release:
needs: test
needs: [test-nodejs]
name: Publish to any of NPM, Github, and Docker Hub

@@ -56,0 +57,0 @@ runs-on: ubuntu-latest

@@ -1,4 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#It does magic only if there is package.json file in the root of the project
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# It does magic only if there is package.json file in the root of the project
name: Version bump - if Node.js project

@@ -13,3 +14,3 @@

version_bump:
name: Generate assets and bump
name: Generate assets and bump NodeJS
runs-on: ubuntu-latest

@@ -16,0 +17,0 @@ steps:

@@ -1,5 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#This action notifies community on slack whenever there is a new issue, PR or discussion started in given repository
# This action notifies community on slack whenever there is a new issue, PR or discussion started in given repository
name: Notify slack

@@ -22,3 +22,3 @@

if: github.event_name == 'issues' && github.actor != 'asyncapi-bot' && github.actor != 'dependabot[bot]' && github.actor != 'dependabot-preview[bot]'
name: On every new issue
name: Notify slack on every new issue
runs-on: ubuntu-latest

@@ -35,3 +35,3 @@ steps:

SLACK_WEBHOOK: ${{secrets.SLACK_GITHUB_NEWISSUEPR}}
SLACK_TITLE: ๐Ÿ› New Issue ๐Ÿ›
SLACK_TITLE: ๐Ÿ› New Issue in ${{github.repository}} ๐Ÿ›
SLACK_MESSAGE: ${{steps.issuemarkdown.outputs.text}}

@@ -42,3 +42,3 @@ MSG_MINIMAL: true

if: github.event_name == 'pull_request_target' && github.actor != 'asyncapi-bot' && github.actor != 'dependabot[bot]' && github.actor != 'dependabot-preview[bot]'
name: On every new pull request
name: Notify slack on every new pull request
runs-on: ubuntu-latest

@@ -55,3 +55,3 @@ steps:

SLACK_WEBHOOK: ${{secrets.SLACK_GITHUB_NEWISSUEPR}}
SLACK_TITLE: ๐Ÿ’ช New Pull Request ๐Ÿ’ช
SLACK_TITLE: ๐Ÿ’ช New Pull Request in ${{github.repository}} ๐Ÿ’ช
SLACK_MESSAGE: ${{steps.prmarkdown.outputs.text}}

@@ -62,3 +62,3 @@ MSG_MINIMAL: true

if: github.event_name == 'discussion' && github.actor != 'asyncapi-bot' && github.actor != 'dependabot[bot]' && github.actor != 'dependabot-preview[bot]'
name: On every new pull request
name: Notify slack on every new pull request
runs-on: ubuntu-latest

@@ -75,4 +75,4 @@ steps:

SLACK_WEBHOOK: ${{secrets.SLACK_GITHUB_NEWISSUEPR}}
SLACK_TITLE: ๐Ÿ’ฌ New Discussion ๐Ÿ’ฌ
SLACK_TITLE: ๐Ÿ’ฌ New Discussion in ${{github.repository}} ๐Ÿ’ฌ
SLACK_MESSAGE: ${{steps.discussionmarkdown.outputs.text}}
MSG_MINIMAL: true

@@ -1,3 +0,3 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -11,3 +11,4 @@ name: Lint PR title

jobs:
lint:
lint-pr-title:
name: Lint PR title
runs-on: ubuntu-latest

@@ -14,0 +15,0 @@ steps:

@@ -1,5 +0,5 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
#This action notifies community on slack whenever there is a new issue, PR or discussion started in given repository
# This action notifies community on slack whenever there is a new issue, PR or discussion started in given repository
name: Notify slack whenever TSC members are mentioned in GitHub

@@ -38,3 +38,3 @@

if: github.event_name == 'issues' && contains(github.event.issue.body, '@asyncapi/tsc_members')
name: On every new issue
name: TSC notification on every new issue
runs-on: ubuntu-latest

@@ -57,3 +57,3 @@ steps:

if: github.event_name == 'pull_request_target' && contains(github.event.pull_request.body, '@asyncapi/tsc_members')
name: On every new pull request
name: TSC notification on every new pull request
runs-on: ubuntu-latest

@@ -76,3 +76,3 @@ steps:

if: github.event_name == 'discussion' && contains(github.event.discussion.body, '@asyncapi/tsc_members')
name: On every new discussion
name: TSC notification on every new discussion
runs-on: ubuntu-latest

@@ -95,3 +95,3 @@ steps:

if: ${{ github.event_name == 'issue_comment' && !github.event.issue.pull_request && contains(github.event.comment.body, '@asyncapi/tsc_members') }}
name: On every new comment in issue
name: TSC notification on every new comment in issue
runs-on: ubuntu-latest

@@ -114,3 +114,3 @@ steps:

if: github.event_name == 'issue_comment' && github.event.issue.pull_request && contains(github.event.comment.body, '@asyncapi/tsc_members')
name: On every new comment in pr
name: TSC notification on every new comment in pr
runs-on: ubuntu-latest

@@ -133,3 +133,3 @@ steps:

if: github.event_name == 'discussion_comment' && contains(github.event.comment.body, '@asyncapi/tsc_members')
name: On every new comment in discussion
name: TSC notification on every new comment in discussion
runs-on: ubuntu-latest

@@ -136,0 +136,0 @@ steps:

@@ -1,3 +0,4 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
name: 'Announce releases in different channels'

@@ -12,3 +13,3 @@

slack:
slack-announce:
name: Slack - notify on every release

@@ -30,3 +31,3 @@ runs-on: ubuntu-latest

twitter:
twitter-announce:
name: Twitter - notify on minor and major releases

@@ -33,0 +34,0 @@ runs-on: ubuntu-latest

@@ -1,3 +0,3 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -28,3 +28,3 @@ name: 'Sentiment Analysis'

jobs:
test:
sentiments:
if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor) }}

@@ -31,0 +31,0 @@ name: Checking sentiments

@@ -1,3 +0,3 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -12,2 +12,3 @@ name: Manage stale issues and PRs

stale:
name: Mark issue or PR as stale
runs-on: ubuntu-latest

@@ -14,0 +15,0 @@ steps:

@@ -1,3 +0,3 @@

#This action is centrally managed in https://github.com/asyncapi/.github/
#Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo
# This action is centrally managed in https://github.com/asyncapi/.github/
# Don't make changes to this file in this repo as they will be overwritten with changes made to the same file in above mentioned repo

@@ -16,2 +16,3 @@ name: Welcome first time contributors

welcome:
name: Post welcome message
if: ${{ !contains(fromJson('["asyncapi-bot", "dependabot[bot]", "dependabot-preview[bot]", "allcontributors"]'), github.actor) }}

@@ -18,0 +19,0 @@ runs-on: ubuntu-latest

{
"name": "@asyncapi/java-spring-cloud-stream-template",
"version": "0.12.1",
"version": "0.13.0",
"description": "Java Spring Cloud Stream template for AsyncAPI generator.",

@@ -37,3 +37,3 @@ "scripts": {

"devDependencies": {
"@asyncapi/generator": "^1.8.25",
"@asyncapi/generator": "^1.9.4",
"@semantic-release/commit-analyzer": "^8.0.1",

@@ -71,3 +71,3 @@ "@semantic-release/github": "^7.0.4",

"generator": {
"generator": ">=1.8.6 <2.0.0",
"generator": ">=1.8.6 <=2.3.0",
"parameters": {

@@ -74,0 +74,0 @@ "actuator": {

@@ -13,3 +13,3 @@ # Java Spring Cloud Stream Generator Template

- 1.8.6 =< [Generator](https://github.com/asyncapi/generator/)
- 1.9.4 =< [Generator](https://github.com/asyncapi/generator/)
- Generator specific [requirements](https://github.com/asyncapi/generator/#requirements)

@@ -16,0 +16,0 @@

@@ -32,3 +32,3 @@ components:

- $ref: '#/components/messages/DogMessage'
asyncapi: 2.0.0
asyncapi: 2.3.0
info:

@@ -35,0 +35,0 @@ description: Testing oneOf

@@ -42,5 +42,5 @@ components:

- DELETE
asyncapi: 2.0.0
asyncapi: 2.3.0
info:
title: solace-test-app
version: 0.0.1

Sorry, the diff of this file is not supported yet