Skip to content

Feat/client#1

Merged
TorinAsakura merged 5 commits intomasterfrom
feat/client
Feb 9, 2026
Merged

Feat/client#1
TorinAsakura merged 5 commits intomasterfrom
feat/client

Conversation

@TorinAsakura
Copy link
Member

No description provided.

@TorinAsakura TorinAsakura self-assigned this Feb 9, 2026
@TorinAsakura TorinAsakura merged commit 9d56162 into master Feb 9, 2026
2 checks passed
@TorinAsakura TorinAsakura deleted the feat/client branch February 9, 2026 13:02
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 27d1649813

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -0,0 +1,21 @@
name: Publish to registry

Choose a reason for hiding this comment

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

P1 Badge Remove duplicated npm publish workflow

Both publish-npm.yaml and publish-npm.yml define the same pull_request.closed trigger and invoke the same reusable publish job, so every merged PR to master will start two publish runs for the same package version. In practice, the first run can publish successfully and the second run then fails on "version already exists", creating flaky/failed release automation for every release.

Useful? React with 👍 / 👎.

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.

1 participant