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

DTL-5457 Install CI/CD for app-extensions-sdk #42

Merged
merged 3 commits into from
Oct 10, 2024
Merged

DTL-5457 Install CI/CD for app-extensions-sdk #42

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b85e7ff
install cicd for app-extensions-sdk
maximlishchenko Oct 8, 2024
a677be2
fix changelog, delete supported_versions in workflow
maximlishchenko Oct 8, 2024
225bb26
upd README.md
maximlishchenko Oct 10, 2024
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
14 changes: 14 additions & 0 deletions .github/workflows/cicd_npm-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
name: Publish NPM Packages

on:
pull_request:
types:
- labeled

jobs:
publish:
if: ${{ github.event.label.name == 'npm-ready-for-publish' }}
uses: pipedrive-actions/github-actions-workflows/.github/workflows/reusable_cicd-npm-publish.yml@master
with:
revision: ${{ github.event.pull_request.head.ref }}
secrets: inherit
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## [Unreleased]

### Changed
- Migrate publish flow from Jenkins to GitHub Actions
- Add devops-tooling as owner for .github/workflows/cicd_*
Copy link
Member

Choose a reason for hiding this comment

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

Is it necessary to include these details in public changelog?

If there even is a need to release a new version, I would keep this information more vague. If it can just be merged to master, then I would exclude adding changelog at all 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I updated the readme to be more vague. The patch label is needed to test that the release process is working.


## [0.10.2] - 2024-05-31

## [0.10.1] - 2024-04-02
Expand Down
3 changes: 2 additions & 1 deletion CODEOWNERS
View file
Open in desktop
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
* @pipedrive/gravity
* @pipedrive/gravity
.github/workflows/cicd_* @pipedrive/devops-tooling
3 changes: 0 additions & 3 deletions Jenkinsfile
View file
Open in desktop

This file was deleted.

3 changes: 3 additions & 0 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,5 +49,8 @@
"rollup-plugin-terser": "^7.0.2",
"tslib": "^2.4.0",
"typescript": "^4.6.2"
},
"publishConfig": {
"access": "public"
}
}
Loading