v6.9.7

6.9.7 (2025-01-17)

Bug Fixes

• audit issues quicktype (#322) (f1339e9)

v6.9.6

6.9.6 (2025-01-07)

Bug Fixes

• elliptic, cross-spawn audit issues (#318) (eac33a3)

v6.10.0-beta.7

6.10.0-beta.7 (2024-08-02)

Bug Fixes

• obfuscation of an array element can lead to undefined error (#312) (51d910e)

v6.10.0-beta.6

6.10.0-beta.6 (2024-07-26)

Bug Fixes

• finalise OA v4.0 context url (#311) (bc62924)

v6.10.0-beta.5

v6.10.0-beta.5 is a manually created Git tag by @HJunyuan

Why?

• The beta branch has been rebased onto master using a force push
• Beta branch commit history no longer has the old tags
• semantic-release will incorrectly attempt to start tagging from v6.10.0-beta.1

Solution

1. Manually created a Git tag v6.10.0-beta.5 on the latest commit of the new beta branch:

   git tag v6.10.0-beta.5 beta
   git push origin tag v6.10.0-beta.5

2. Manually created a Git note on the same commit (as required by semantic-release):

   git fetch origin refs/notes/semantic-release:refs/notes/semantic-release
   git notes --ref="semantic-release" add -f -m '{"channels":["beta"]}' v6.10.0-beta.5
   git push origin refs/notes/semantic-release

Drawback

• semantic-release will not automatically publish v6.10.0-beta.5 onto NPM - https://github.com/Open-Attestation/open-attestation/actions/runs/10089589374/job/27897818350#step:6:34
• Can be done so manually if really required

Reference

• https://semantic-release.gitbook.io/semantic-release/support/troubleshooting#release-not-found-release-branch-after-git-push-force
• https://gist.github.com/topheman/ec8cde7c54e24a785e52

v6.9.5

6.9.5 (2024-07-23)

Bug Fixes

• ws security advisory from ethers v5 (239bdba)

v6.9.4

6.9.4 (2024-07-22)

Bug Fixes

• accept application/ld+json when fetching context (#307) (f783b3c)

v6.10.0-beta.4

6.10.0-beta.4 (2024-05-31)

Bug Fixes

• ajv-formats should be a dependency (#300) (#303) (0dbdadd)

v6.9.3

6.9.3 (2024-05-31)

Bug Fixes

• ajv-formats should be a dependency (#300) (d1c1684)

v6.10.0-beta.3

6.10.0-beta.3 (2024-05-20)

Bug Fixes

• install command to target beta release (#299) (ab9a908)