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

Jump to bottom

ci: Create a shared GitHub + NPM release workflow. #25

Merged
merged 4 commits into from
Sep 24, 2024
Merged

ci: Create a shared GitHub + NPM release workflow. #25

merged 4 commits into from
Sep 24, 2024

Conversation

Zurcusa
Copy link
Collaborator

@Zurcusa Zurcusa commented Sep 24, 2024

Description

Fruzhin-web needs to create both GitHub and NPM releases. This PR implements the CI/CD needed to do that.

  • What does this PR do?
    Adds a shared workflow that creates a GitHub tag and optional github release + npm release.
  • Why are these changes needed?
    To improve current CI/CD.
  • How were these changes implemented and what do they affect?
    Using GitHub actions.

Fixes LimeChain#530

Checklist:

  • I have read the contributing guidelines.
  • My PR title matches the Conventional Commits spec.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@Zurcusa Zurcusa self-assigned this Sep 24, 2024
@Zurcusa Zurcusa merged commit 40cc9d2 into dev Sep 24, 2024
1 check passed
@Zurcusa Zurcusa deleted the 530-npm-release branch September 24, 2024 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Grigorov-Georgi Grigorov-Georgi Grigorov-Georgi approved these changes

Assignees

@Zurcusa Zurcusa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Release to NPM >> GitHub workflows
2 participants
@Zurcusa @Grigorov-Georgi