Skip to content

Conversation

@JiriLojda
Copy link
Member

Motivation

Which issue does this fix? Fixes #issue number

If no issue exists, what is the fix or new feature? Were there any reasons to fix/implement things that are not obvious?

Checklist

  • Code follows coding conventions held in this repo
  • Automated tests have been added
  • Tests are passing
  • Docs have been updated (if applicable)
  • Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test

If manual testing is required, what are the steps?

@JiriLojda JiriLojda requested a review from a team as a code owner October 15, 2025 14:57
@JiriLojda JiriLojda force-pushed the add-GH-registry-publishing branch from 084b5ba to edfe6c6 Compare October 21, 2025 19:14
Sync package version across package.json, package-lock.json, and server.json files

Add shttp package to server.json

Make sure syncVersion works with multiple packages in server.json

Refactor syncVersion.ts

Describe release process in readme

Fix formatting in server.json

Remove development env variables from server.json

Sync server.json version

Fix server.json format and ensure npm version doesn't break server.json formatting
@JiriLojda JiriLojda force-pushed the add-GH-registry-publishing branch from a843887 to 8e6c78e Compare October 21, 2025 19:29
@JiriLojda JiriLojda merged commit edc8429 into master Oct 21, 2025
3 checks passed
@JiriLojda JiriLojda deleted the add-GH-registry-publishing branch October 21, 2025 19:30
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.

3 participants