Skip to content

feat(pipeline): set publish pipeline trigger as manual#16

Open
KingPepito wants to merge 1 commit into
mainfrom
feat/MJINT-175_Import_MCP_on_resources_server
Open

feat(pipeline): set publish pipeline trigger as manual#16
KingPepito wants to merge 1 commit into
mainfrom
feat/MJINT-175_Import_MCP_on_resources_server

Conversation

@KingPepito

Copy link
Copy Markdown
Collaborator
  • Remove tag based package publish, now trusting package.json version.
  • Use manual trigger for publish workflow.
  • Add security to ensure package version is bumped.

@KingPepito
KingPepito requested a review from a team as a code owner July 21, 2026 11:00
- Remove tag based package publish, now trusting package.json version.
- Use manual trigger for publish workflow.
- Add security to ensure package version is bumped.
@KingPepito
KingPepito force-pushed the feat/MJINT-175_Import_MCP_on_resources_server branch from b385ce5 to 2683570 Compare July 21, 2026 11:02
workflow_dispatch:

jobs:
publish:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

We could also restrict this to just main or prerelease branches. What do you think? Something like this

Suggested change
publish:
publish:
if: github.ref == 'refs/heads/main'

@KingPepito KingPepito Jul 21, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I was also considering it at some point, but now this package is a dep for our resources server, that might be a little too restrictive at the moment. Specifically now we are in the middle of mcp project.

Thing that made me drop the idea is that I remembered I recently needed to publish an alpha/beta only for staging env testing purpose. I would not want to cause some pollution to the main branch in case we need some back and forth to adjust. Does that seems reasonable to you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants