Add publishing set up with Mono #35
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a `mono.yml` configuration file so that it works with Mono. https://github.com/appsignal/mono/ Use changesets to generate changesets and bump the version number. See the Mono README for more information. I changed the committed version down to 0.1.0 and added a changeset for a major version bump so the next version will be version 1.0.0 on npm. Closes #33
With this workflow, when a new Git tag is pushed, we automatically create a Pull Request on the appsignal.com/changelog page with the new release.
tombruijn
added
the
dev happiness
Automatically create a GitHub release on the Git tag push event. It will use the updated changelog content as the release description.
If we keep the publish workflow as is it won't be triggers as one GitHub Actions workflow can't trigger another workflow through an event like creating a release on the repo, like I did in the previous commit. Update the publish workflow to also listen to the tag push event. I've also updated the `latest` tag push logic with the help of Claude to figure out a way to not publish the `latest` tag when a release is a prerelease.
|
Please note, this may not work on the first try. GitHub Actions remain tricky. So, it would make sense if I publish the release and immediately fix anything that comes up. |
|
@matsimitsu I think we should rename the package in |
|
@tombruijn I don't think so, docker just runs the index.js without caring for the package name. |
This name fits better with our existing naming scheme for packages.
|
Okay, I've updated the name. I'll merge it once approved, and publish it |
matsimitsu
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add mono configuration for publishing
Add a
mono.ymlconfiguration file so that it works with Mono. https://github.com/appsignal/mono/Use changesets to generate changesets and bump the version number. See the Mono README for more information.
I changed the committed version down to 0.1.0 and added a changeset for a major version bump so the next version will be version 1.0.0 on npm.
Closes #33
Add GitHub workflow for changelog PR generation
With this workflow, when a new Git tag is pushed, we automatically create a Pull Request on the appsignal.com/changelog page with the new release.
Create a GitHub release from the tag on push
Automatically create a GitHub release on the Git tag push event. It will use the updated changelog content as the release description.
Update the publish workflow to listen to tags
If we keep the publish workflow as is it won't be triggers as one GitHub Actions workflow can't trigger another workflow through an event like creating a release on the repo, like I did in the previous commit.
Update the publish workflow to also listen to the tag push event.
I've also updated the
latesttag push logic with the help of Claude to figure out a way to not publish thelatesttag when a release is a prerelease.Rename to
@appsignal/mcppackageThis name fits better with our existing naming scheme for packages.