Release rmdv v0.7.0 - #24
Conversation
|
@codex review |
![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: ec8809cdbe
ℹ️ 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".
| "acceptedAnswer": { | ||
| "@type": "Answer", | ||
| "text": "On macOS, download the signed and notarized .dmg from github.com/minchenlee/rmdv/releases and drag rmdv to Applications. After opening the app, use Install CLI from the command palette to expose rmdv in /usr/local/bin. On Linux, download the x86_64 AppImage, launch it once, and use Install CLI from the command palette to create ~/.local/bin/rmdv; add ~/.local/bin to PATH if needed. To build from source, install Rust 1.80 or newer, then run: git clone https://github.com/minchenlee/rmdv && cd rmdv && cargo build --release. Windows builds use cargo build --release --no-default-features because PDF extraction is macOS/Linux only." | ||
| "text": "On macOS, download the .dmg from github.com/minchenlee/rmdv/releases, check that release's signing/notarization status, and drag rmdv to Applications. After opening the app, use Install CLI from the command palette to expose rmdv in /usr/local/bin. On Linux, download the x86_64 AppImage, launch it once, and use Install CLI from the command palette to create ~/.local/bin/rmdv; add ~/.local/bin to PATH if needed. To build from source, install Rust 1.80 or newer, then run: git clone https://github.com/minchenlee/rmdv && cd rmdv && cargo build --release. Windows builds use cargo build --release --no-default-features because PDF extraction is macOS/Linux only." |
There was a problem hiding this comment.
When the v0.7 tag runs, .github/workflows/release.yml:347-359 creates the GitHub Release with generated notes and assets only; it neither consumes the new release-notes file nor publishes the post-verification signing/notarization result, and no other release-edit step exists. The linked release therefore does not provide the status this install copy tells users to check—especially if the workflow uses its ad-hoc-signing fallback—so add a publication step/body containing the verified state or avoid this claim.
AGENTS.md reference: site/AGENTS.md:L51-L53
Useful? React with 👍 / 👎.
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0a6cd53b7c
ℹ️ 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".
| 1. Run native GUI interaction smoke on the exact packaged v0.7.0 candidate and | ||
| obtain owner acceptance. | ||
| 2. Commit/push/open the release PR, then merge only after GUI smoke plus | ||
| exact-head review and CI pass; proceed through the already-authorized tag, |
There was a problem hiding this comment.
The commit's validation records exact packaged-app GUI smoke plus exact-head review and two successful CI runs, but this new routing snapshot still tells the next owner to run that smoke and open the release PR; the MDV-020 plan likewise leaves those gates unchecked and calls them blockers. After merge, anyone following the required first-pass status will be routed backward instead of to the remaining tag/artifact/deployment gates, so update the status and plan with the evidence already obtained.
AGENTS.md reference: AGENTS.md:L29-L34
Useful? React with 👍 / 👎.
1 participant
Summary
v0.7.0package, release-note, content-pack, and site metadataMDV-017) and Theme Settings/Studio (MDV-019)Included user-facing changes
Excluded
MDV-017)MDV-019)No product implementation under
src/or tests is changed by this release-preparation branch.Validation
cargo checkcargo check --no-default-featurescargo test --lib— 361 passedcargo test --tests— all integration targets passedcargo build --release --bin rmdv.apppackaging with embedded PDFium and structural codesign verification0.7.0app:document-mindmap.mdFile and folder refreshedandFile path copied1collapsed to the root and depth0restored branches1–6plusShow All Node Levelsnode --check site/app.jsnode --check site/check-shortcuts.mjsnode site/check-shortcuts.mjsgit diff --checkRemaining release gates
llms.txtverification