Skip to content

ci: Set up automated checks and npm publishing - #61

Merged
metalwarrior665 merged 1 commit into
masterfrom
set-up-ci
Mar 18, 2026
Merged

metalwarrior665 merged 1 commit into
masterfrom
set-up-ci

Conversation

@janbuchar

Copy link
Copy Markdown
Collaborator
  • As discussed with @ruocco-l, this adds automated code checks and npm publishing
  • I'm pretty sure this won't work on the first try, but it's better to fix it when problems appear instead of wasting too much time trying to review it in depth

@janbuchar janbuchar added t-tooling Issues with this label are in the ownership of the tooling team. adhoc Ad-hoc unplanned task added during the sprint. labels Mar 18, 2026
@janbuchar
janbuchar requested review from metalwarrior665 and ruocco-l and removed request for ruocco-l March 18, 2026 14:27

@metalwarrior665 metalwarrior665 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks. I assume this is ± copied from our other packages.

Am I correct that it works as this?

  • Every commit to master is beta package release
  • Every commit with package.json version bump releases that version

@janbuchar

Copy link
Copy Markdown
Collaborator Author
* Every commit to master is beta package release

Yes.

* Every commit with package.json version bump releases that version

No, package.json bumps are done on each commit to master, along with updating the changelog. Then, when you want to do a stable release, you manually dispatch the manual_release_stable workflow and that releases the version determined using conventional commits, or you can just specify the exact version yourself.

@metalwarrior665

Copy link
Copy Markdown
Member

Ok, so let's try this. The failing tests don't matter now, I will fix that later.

@metalwarrior665
metalwarrior665 merged commit 42fe0ad into master Mar 18, 2026
2 of 10 checks passed
@janbuchar

Copy link
Copy Markdown
Collaborator Author

The failing tests will probably prevent the publishing workflow from running though...

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

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants