Release packages#17
Merged
lucasvinhas merged 1 commit intomainfrom Feb 5, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
907c5eb to
d397421
Compare
![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: d397421060
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Comment on lines
2
to
4
| "name": "@oaknetwork/contracts", | ||
| "version": "0.1.0-dev.1", | ||
| "version": "0.1.0", | ||
| "description": "TypeScript SDK for Oak Network smart contracts", |
There was a problem hiding this comment.
The package version is set to 0.1.0, but the same changelog already lists a prior 1.0.0 release (see packages/contracts/CHANGELOG.md), which means this change is a version downgrade. If 1.0.0 has been published, npm will reject publishing 0.1.0; even if it hasn’t, the version history becomes inconsistent. Consider bumping to a version higher than 1.0.0 or correcting the changelog/history before release.
Useful? React with 👍 / 👎.
lucasvinhas
added a commit
that referenced
this pull request
Feb 5, 2026
* docs: update README with work in progress note and launch timeline * chore: enhance release workflow to build and publish packages conditionally Updated the GitHub Actions workflow to include conditional steps for building and publishing packages only when there are no changesets. Added steps for creating GitHub releases and tagging versions based on package.json files. * chore: update release workflow to configure npm registry for OIDC Added a step to set up the npm registry configuration for OIDC in the release workflow, ensuring proper publishing of packages when there are no changesets. * chore: update release workflow to install latest npm version for OIDC support Modified the release workflow to install the latest version of npm and removed the explicit npm registry configuration step, ensuring compatibility with OIDC during package publishing. * chore: modify release workflow to conditionally publish packages based on version Updated the release workflow to check the package version before publishing. If the version includes a pre-release tag, it publishes with the 'dev' tag; otherwise, it publishes normally. This ensures proper version handling during the release process. * chore: add repository metadata to package.json files for api and contracts Included repository information in the package.json files for both the api and contracts packages, specifying the git type, URL, and directory. This enhances package metadata for better integration and visibility. * chore: bump version to 0.1.0-dev.1 in package.json for contracts * chore: add testing changeset for minor version updates in api and contracts * chore: version packages (#17) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * chore: update version to 0.1.0 in package.json for api * chore: refactor release workflow to publish all packages conditionally Updated the release workflow to publish all packages in the 'packages' directory, checking for existing published versions and using the appropriate tag for pre-release versions. This enhances the publishing process by ensuring only new versions are published and improves overall efficiency. * chore: enhance httpClient to include Oak-Version in headers Refactored the httpClient to automatically include the Oak-Version header in all requests, utilizing the version from package.json or an environment variable. Updated unit tests to verify the correct headers are sent, ensuring consistency across API calls. * test: add fallback mechanism for Oak-Version in httpClient tests Implemented a new test case to verify that the httpClient correctly falls back to using 'unknown' for the Oak-Version header when both the environment variable and package.json are unavailable. This enhances the robustness of the httpClient by ensuring it handles versioning gracefully in edge cases. * chore: add changeset for Oak-Version header enhancement in httpClient --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@oaknetwork/api@1.1.0
Minor Changes
Minor Changes
@oaknetwork/contracts@0.1.0
Minor Changes
Minor Changes