Repository navigation
Add missing changeset and update node version to 22 - #597
Conversation
🦋 Changeset detectedLatest commit: f959b98 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
View your CI Pipeline Execution ↗ for commit f959b98
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud is proposing a fix for your failed CI:
We fixed the failing javascript-sdk:test run by running device.store.test.ts in the node vitest environment instead of jsdom. This avoids the jsdom/undici AbortSignal mismatch that made the RTK Query requests fail and return no data. With these changes, all 158 tests pass locally and lint passes.
Tip
✅ We verified this fix by re-running javascript-sdk:test.
diff --git a/packages/javascript-sdk/src/device-client/device.store.test.ts b/packages/javascript-sdk/src/device-client/device.store.test.ts
index 897e45b..c60d2a2 100644
--- a/packages/javascript-sdk/src/device-client/device.store.test.ts
+++ b/packages/javascript-sdk/src/device-client/device.store.test.ts
@@ -1,3 +1,4 @@
+// @vitest-environment node
/*
* @forgerock/javascript-sdk
*
diff --git a/packages/javascript-sdk/vitest.setup.ts b/packages/javascript-sdk/vitest.setup.ts
index 644736e..6677b41 100644
--- a/packages/javascript-sdk/vitest.setup.ts
+++ b/packages/javascript-sdk/vitest.setup.ts
@@ -1 +1,4 @@
-import 'vitest-canvas-mock';
+// Some suites opt into the node environment (no `window`), e.g. when using Node's native fetch
+if (typeof window !== 'undefined') {
+ await import('vitest-canvas-mock');
+}
Or Apply changes locally with:
npx nx-cloud apply-locally SS5U-j5aM
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 Learn more about Self-Healing CI on nx.dev
SteinGabriel
left a comment
There was a problem hiding this comment.
CONTRIBUTING.md:16 still says "Node 20" instead of 22. Other than that, it looks ready to merge.
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #597 +/- ##
===========================================
- Coverage 56.72% 56.58% -0.15%
===========================================
Files 105 105
Lines 28457 28534 +77
Branches 1644 1644
===========================================
+ Hits 16143 16145 +2
- Misses 12314 12389 +75 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
cerebrl
left a comment
There was a problem hiding this comment.
This PR looks fine, but I have a question about the Changeset not really describing what's in this PR.
| '@forgerock/token-vault': patch | ||
| --- | ||
|
|
||
| Compose AM request URLs from config to prevent attacker-supplied request URLs |
There was a problem hiding this comment.
This Changeset is a little confusing for me. Did we not include a Changeset with the original PR?
There was a problem hiding this comment.
Nope. Not one that I could find. Unless it the original fix was already released in which case the changeset would have been automatically deleted.
There was a problem hiding this comment.
We will need to stub out the changeset in this PR and then manually change the commit SHA in the release PR later so it's tied to the right commit. See this discussion: https://pingidentity.slack.com/archives/C0ANZ21HKCH/p1792080788495179
There was a problem hiding this comment.
I think this is from Claude. Can we gitignore this folder?
There was a problem hiding this comment.
This file can also be deleted if the migration completed successfully
There was a problem hiding this comment.
I swear I tried this but tests were still failing randomly for me, ughhh
8325dcd to
2fd8352
Compare
chore: fix - upgrade nx - fix ci - fix node issues and upgrade to node 24
2fd8352 to
f959b98
Compare
JIRA Ticket
Description