-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: Release V2.1.0 #3
Conversation
… to v3 in two actions.
fix: Remove deprecated codeql action v2 in workflows
|
||
`push`: | ||
|
||
`branches`: [ "dev", "main" ] - The workflow triggers when code is pushed to the dev or main branches. |
Check warning
Code scanning / Remark-lint (reported by Codacy)
Warn when references to undefined definitions are found. Warning
|
||
`pull_request`: | ||
|
||
`branches`: [ "dev" ] - The workflow triggers when a pull request is opened or updated against the dev branch. |
Check warning
Code scanning / Remark-lint (reported by Codacy)
Warn when references to undefined definitions are found. Warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Markdownlint (reported by Codacy) found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
…changelog after a release
feat: implement automated release management improvements
fix: fix the yaml syntax error because of multiple if statements and add codeowners files
fix: Update and optimise workflows before syncing them across tazama-lf repos
fix: update tag to reflect upcoming release
fix: Add rule-901 repo to sync-workflow
… because the file have been copied to repos that need to use it
fix: use the correct scope for npm publishing workflow
SPDX-License-Identifier: Apache-2.0
What did we change?
Create Tazama Release V2.1.0
How was it tested?