Release fmrireg 0.3.0 - #244
Conversation
0.2.0 was never tagged or released (the last tag is v0.1.2), so the unreleased changes collected under the 0.2.0 NEWS heading ship as 0.3.0. Retitle that heading, and move the README status line and the coef() orientation-change section to 0.3.0, the first release with that change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: bbad3d91a1
ℹ️ 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".
| Type: Package | ||
| Title: Regression Analysis of Functional Magnetic Resonance Imaging Data | ||
| Version: 0.2.0 | ||
| Version: 0.3.0 |
There was a problem hiding this comment.
When this release is tagged on its merge commit as described, DESCRIPTION will report 0.3.0 while the same tagged tree's codemeta.json still reports 0.2.0 (including its package description). The update in .github/workflows/update-codemeta.yaml runs only after the push to main and creates a later commit, so it cannot repair metadata at an already-created release tag; regenerate codemeta.json in the release commit or place the tag on the generated follow-up commit.
Useful? React with 👍 / 👎.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
1 participant
Bumps the version to 0.3.0.
DESCRIPTION:Version: 0.2.0→0.3.0.NEWS.md: the top heading# fmrireg 0.2.0→# fmrireg 0.3.0. The last tag isv0.1.2and 0.2.0 was never tagged or released, so everything collected under that heading ships as 0.3.0.README.mdstatus line: 0.3.0.?coef.fmri_lm"Orientation change" section (roxygen source and Rd): 0.2.0 → 0.3.0, since 0.3.0 is the first release carrying that change.codemeta.jsonis left to the GitHub Action that regenerates it.After merge: tag
v0.3.0on the merge commit.Downstream
fmrireg (>= 0.2.0)floors (e.g. fmrialigned) remain satisfied. Independent of #243, which only touchesRemotes; either can merge first.🤖 Generated with Claude Code