Skip to content

feat: change schemaIds -> intentIds for Frequency 2.x#455

Merged
JoeCap08055 merged 17 commits intomainfrom
chore/upgrade-frequency-2.0
Feb 6, 2026
Merged

feat: change schemaIds -> intentIds for Frequency 2.x#455
JoeCap08055 merged 17 commits intomainfrom
chore/upgrade-frequency-2.0

Conversation

@JoeCap08055
Copy link
Contributor

@JoeCap08055 JoeCap08055 commented Dec 22, 2025

This PR implements the changes necessary for SIWF to work properly with Frequency 2.x, notably:

  • In the AddProvider payload, change the name of the field schemaIds -> intentIds
  • Update Secp256k1 signatures in tests, docs, etc
  • Update docs

Closes #457

node-version: ${{ inputs.node-version }}
cache: ${{ inputs.cache }}
cache-dependency-path: ${{ inputs.cache-dependency-path }}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't want to change the npm version globally, because it causes compatibility issues with the lock files. We only need >= 11.x for the publishing step.

Comment on lines -27 to -30
strategy:
matrix:
node-version: [20.x]
# See supported Node.js release schedule at https://nodejs.org/en/about/releases/
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Doesn't make sense to use a matrix here; we only publish one version of the package. I left the matrix in other parts of the pipeline, because it's okay to validate our build on different versions of Node, but for publishing, just like Highlander, there can be only one.

strategy:
matrix:
node-version: [20.x, 22.x]
node-version: [22.x]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed validating against Node 20.x, since it's EOL. Adding support for Node 24.x can be a future task.

@JoeCap08055 JoeCap08055 requested a review from a team February 5, 2026 19:39
@JoeCap08055 JoeCap08055 marked this pull request as ready for review February 5, 2026 19:43
Copy link
Contributor

@enddynayn enddynayn left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@shannonwells shannonwells left a comment

Choose a reason for hiding this comment

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

  • reviewed the code changes
  • checked out the branch
  • built the js lib
  • built and ran the mock server
  • built and ran js-example tool
  • built and ran signed request generator and used it to generate a signature with PolkadotJS extension.

@JoeCap08055 JoeCap08055 enabled auto-merge (squash) February 6, 2026 16:06
@JoeCap08055 JoeCap08055 merged commit 81fd8a5 into main Feb 6, 2026
7 checks passed
@JoeCap08055 JoeCap08055 deleted the chore/upgrade-frequency-2.0 branch February 6, 2026 21:11
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.

[chore]: Cut a new release compatible with Frequency 2.0.0

3 participants