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: OBS-392 Semantic release bare bones for monorepo. #16

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

natm
Copy link
Member

@natm natm commented Feb 13, 2024

Basics copied in for releasing individual components.

Uses semantic-release-monorepo a plugin for semantic-release.

For each component:

  • Github release workflow, scoped for the component path, e.g. diode-python-sdk/**
  • .releaserc.json, has the component name and tagging template
  • package.json, versions of the semantic release NPM packages to use.

Copied in @rcrawf's reusable "next version" and "release" workflows. The next version item is important as we can use the output from it during the build step to inject version files / build parameters.

Copy link

linear bot commented Feb 13, 2024

@natm
Copy link
Member Author

natm commented Feb 13, 2024

I added a new repo secret SLACK_OBSERVABILITY_RELEASE_WEBHOOK which points to a new Slack webhook in the #engineering-observability-github channel.

@mfiedorowicz mfiedorowicz merged commit c0a51f1 into develop Feb 13, 2024
9 checks passed
@mfiedorowicz mfiedorowicz deleted the feat/OBS-392_semantic_release branch February 13, 2024 13:10
@orb-ci
Copy link

orb-ci commented Feb 13, 2024

🎉 This PR is included in version diode-sdk-python-v1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@orb-ci
Copy link

orb-ci commented Feb 13, 2024

🎉 This PR is included in version diode-netbox-plugin-v1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

3 participants