Archive mpp-abstract and switch publish flow to main#16
Conversation
- Add archive notice and contributing guidance - Redirect README and package docs to Abstract-Foundation/abstract-packages
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 697180756e
ℹ️ 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".
| published_version=$(npm view @abstract-foundation/mpp version 2>/dev/null || true) | ||
| published_version=$(printf '%s\n' "$published_version" | tail -n 1 | tr -d '"') | ||
|
|
||
| should_publish=false | ||
| if [ -z "$published_version" ] || [ "$published_version" != "$local_version" ]; then |
There was a problem hiding this comment.
The detect step compares local_version against npm view ... version, which only yields a single version string, so any already-published non-latest version is treated as "unpublished" and triggers should_publish=true. If main is reverted/cherry-picked to an older version that already exists on npm, this workflow will run verify/publish and then fail at publish with a duplicate-version error instead of correctly skipping.
Useful? React with 👍 / 👎.
1 participant
Summary
Abstract-Foundation/abstract-packagesin the README and release docs..tsbuildinfoartifacts.Testing