Skip to content

fix(test): adopt effect-rstest PR #4 canary and drop the pnpm patch - #871

Merged
BleedingDev merged 2 commits into
mainfrom
fix/507-effect-rstest-canary
Sep 19, 2026
Merged

BleedingDev merged 2 commits into
mainfrom
fix/507-effect-rstest-canary

Conversation

@BleedingDev

@BleedingDev BleedingDev commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Closes TechsioCZ/ontos#507 — Remove temporary effect-rstest patch after upstream fixes merge.

Why the patch was still needed on main

  • npm effect-rstest@0.1.4 (pinned since 3b9f684) is published from github.com/Nsttt/effect-rstest, not ScriptedAlchemy, on 2026-09-08 13:34Z — before ScriptedAlchemy/effect-rstest PR #4 merged (20:29Z, f29b3f49). Its dist still has isEqual(a) || isEqual(b), no onTestFinished settlement and no setup-fiber interruption, so main carried a 68-line re-application of the fixes as patches/effect-rstest@0.1.4.patch.
  • ScriptedAlchemy has published no npm release or tag. The only immutable artifact containing PR Ticketing: Mandatory property validation #4 is the merged-commit canary https://pkg.pr.new/ScriptedAlchemy/effect-rstest@f29b3f495d45a11037334620bf5f693414fb5578 (verified: all three fix markers present, it.prop schema support included, exports ././utils only — the repo imports only 'effect-rstest'; peers @rstest/core ^0.11.11, effect ^4.0.0-rc.108).

Change

  • Pin the f29b3f49 canary in all 11 consuming manifests.
  • Remove effect-rstest@0.1.4 from patchedDependencies and delete patches/effect-rstest@0.1.4.patch.
  • Regenerate pnpm-lock.yaml; pnpm install --frozen-lockfile succeeds without the patch. No @app/effect-rstest alias or vendored copy is restored.

Verification (local, against the installed package)

  • scripts/tests/effect-rstest-package.test.mts (equality tester, tuple/record schema props, discarded success values, timed-out finalizer settlement): 7/7 pass
  • pnpm test:scripts 335/335 · pnpm test:unit all workspace projects pass · pnpm test:generation 143/143 · pnpm test:deployment-impact 43/43
  • pnpm typecheck ✅ · pnpm lint && pnpm format:check ✅ · pnpm typecheck:lint-rules && pnpm test:lint-rules 217/217 ✅
  • Service integration (pnpm test:integration, Postgres-backed) not run locally — no local database; relies on CI.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the test tooling to a commit-pinned preview build across the project.
    • Removed the previous local patch associated with the published test tooling version.

npm effect-rstest@0.1.4 predates upstream PR #4 and lacks its fixes, which is
why main still carried patches/effect-rstest@0.1.4.patch. Pin the immutable
merged-commit canary f29b3f49 that contains Effect equality, scoped test
lifetimes and timed-out settlement upstream, remove the patch and its
patchedDependencies entry, and regenerate the lockfile.

Closes #507

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@semanticdiff-com

semanticdiff-com Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-19T09:02:46.772834Z 3160860 New commits
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

Warning

Review limit reached

Next included review available in 55 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 37dd5a96-214b-461b-b289-d28e835e553d

📥 Commits

Reviewing files that changed from the base of the PR and between 45a0c95 and 3160860.

📒 Files selected for processing (1)
  • app/tools/oxlint/effect-native/README.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 94d59b2c-6cf1-46b0-af91-7e70b7420e94

📥 Commits

Reviewing files that changed from the base of the PR and between 27800ea and 45a0c95.

⛔ Files ignored due to path filters (1)
  • app/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (13)
  • app/apps/shell-super-app/package.json
  • app/package.json
  • app/packages/core-runtime/package.json
  • app/packages/customer-payment-term-contracts/package.json
  • app/packages/email-delivery/package.json
  • app/packages/gateway-principal-verifier/package.json
  • app/packages/payment-term-catalog-contracts/package.json
  • app/packages/shared-contracts/package.json
  • app/patches/effect-rstest@0.1.4.patch
  • app/pnpm-workspace.yaml
  • app/verticals/commerce-customer-context/package.json
  • app/verticals/party-registry/package.json
  • app/verticals/payment-term-catalog/package.json
💤 Files with no reviewable changes (2)

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (14)
  • GitHub Check: OntOS API Boundary Rules
  • GitHub Check: Codesmith and Generation Tests
  • GitHub Check: Repository Tooling Tests
  • GitHub Check: Typecheck
  • GitHub Check: Deployment Impact Planner Tests
  • GitHub Check: Module Entrypoint Contracts
  • GitHub Check: Complete Unit and Component Tests
  • GitHub Check: Lint
  • GitHub Check: Database Access Boundaries
  • GitHub Check: Effect Rule Implementation
  • GitHub Check: Cloudflare Workerd Artifact Proof
  • GitHub Check: Node Backend Federation Artifact Proof
  • GitHub Check: Database, Migration, RLS, Authorization, and Outbox Integration
  • GitHub Check: Quality Audit Guardrails
🧰 Additional context used
📓 Path-based instructions (1)
Before changing files under `app/`, read [the application coding guide](./README.md).

📄 CodeRabbit inference engine (app/AGENTS.md)

Files:

  • app/verticals/party-registry/package.json
  • app/packages/gateway-principal-verifier/package.json
  • app/packages/shared-contracts/package.json
  • app/verticals/commerce-customer-context/package.json
  • app/packages/payment-term-catalog-contracts/package.json
  • app/packages/email-delivery/package.json
  • app/package.json
  • app/apps/shell-super-app/package.json
  • app/verticals/payment-term-catalog/package.json
  • app/packages/customer-payment-term-contracts/package.json
  • app/packages/core-runtime/package.json
🔇 Additional comments (11)
app/package.json (1)

107-107: LGTM!

app/apps/shell-super-app/package.json (1)

84-84: LGTM!

app/packages/core-runtime/package.json (1)

54-54: LGTM!

app/packages/customer-payment-term-contracts/package.json (1)

26-26: LGTM!

app/verticals/party-registry/package.json (1)

103-103: LGTM!

app/verticals/payment-term-catalog/package.json (1)

64-64: LGTM!

app/packages/email-delivery/package.json (1)

21-21: LGTM!

app/packages/gateway-principal-verifier/package.json (1)

22-22: LGTM!

app/packages/payment-term-catalog-contracts/package.json (1)

27-27: LGTM!

app/packages/shared-contracts/package.json (1)

30-30: LGTM!

app/verticals/commerce-customer-context/package.json (1)

189-189: LGTM!


Walkthrough

The change updates all effect-rstest development dependencies to a commit-pinned pkg.pr.new build. It removes the temporary effect-rstest patch and its workspace mapping.

Changes

effect-rstest adoption

Layer / File(s) Summary
Pin consuming manifests
app/package.json, app/apps/shell-super-app/package.json, app/packages/*/package.json, app/verticals/*/package.json
All listed effect-rstest development dependencies now use the preview build pinned to commit f29b3f495d45a11037334620bf5f693414fb5578 instead of 0.1.4.
Remove temporary patch
app/patches/effect-rstest@0.1.4.patch, app/pnpm-workspace.yaml
The local patch is removed, including its test settlement, equality, and scoped setup changes. The corresponding patchedDependencies entry is also removed.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Linked Issues check ❓ Inconclusive The changes satisfy the main coding requirements in issue #507. All 11 consuming manifests use the immutable pkg.pr.new canary at commit f29b3f495d45a11037334620bf5f693414fb5578. The `patchedDepen… Provide successful CI results for the required Postgres-backed service integration tests, including the specified worker and browser-retry settings, or provide equivalent reviewable evidence that those tests passed.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarises the main changes: adopting the effect-rstest PR #4 canary and removing the pnpm patch.
Out of Scope Changes check ✅ Passed The changed files support issue #507. The manifest updates adopt the immutable canary. The workspace change removes the temporary patch mapping. The patch deletion removes the temporary implementation…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Full details: Linked Issues check

Explanation

The changes satisfy the main coding requirements in issue #507. All 11 consuming manifests use the immutable pkg.pr.new canary at commit f29b3f495d45a11037334620bf5f693414fb5578. The patchedDependencies entry and patch file were removed. The PR summary states that the lockfile was regenerated and that frozen installation succeeds without the patch. It also states that the canary contains the equality, schema-property, discarded-success, timeout-settlement, and setup-interruption fixes. Typecheck, lint, lint-rule, unit, component, tooling, generation, and related checks passed. However, Postgres-backed service integration tests were not run locally, and no CI result is supplied. Full compliance with the test requirement cannot be confirmed.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
✨ Simplify code
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Copy link
Copy Markdown

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: 45a0c95e0a

ℹ️ 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".

Comment thread app/package.json
},
"devDependencies": {
"effect-rstest": "0.1.4",
"effect-rstest": "https://pkg.pr.new/ScriptedAlchemy/effect-rstest@f29b3f495d45a11037334620bf5f693414fb5578",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Refresh the test-runtime guidance after removing the patch

When maintainers consult app/tools/oxlint/effect-native/README.md:84, it still states that the current canary uses a temporary pnpm patch and that issue #507 tracks deleting it. This commit pins the unpatched canary and closes that issue, so the authoritative guidance now contradicts the dependency configuration and can prompt someone to restore an obsolete patch; update that paragraph as part of this migration.

AGENTS.md reference: app/AGENTS.md:L3-L3

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 3160860: the paragraph now describes the unpatched canary pin, points at the installed-package guard test, and warns that npm effect-rstest releases are a separate publishing line without these fixes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@BleedingDev
BleedingDev merged commit 1a07b78 into main Sep 19, 2026
23 checks passed
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.

Remove temporary effect-rstest patch after upstream fixes merge

1 participant