Skip to content

Bump libocr which has a critical ocr3.1 fix needed for Vault #20985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
prashantkumar1982 merged 1 commit into from
Jan 30, 2026
Merged

Bump libocr which has a critical ocr3.1 fix needed for Vault #20985

prashantkumar1982 merged 1 commit into from
Jan 30, 2026

Conversation

@prashantkumar1982
Copy link
Contributor

@prashantkumar1982 prashantkumar1982 commented Jan 30, 2026 •
edited
Loading

Vault OCR contract upgrade requires this new libocr fix onto all Vault nodes

@prashantkumar1982 prashantkumar1982 changed the title Bump libocr which has a critical 3.1 fix needed for Vault Bump libocr which has a critical ocr3.1 fix needed for Vault Jan 30, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 30, 2026

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@prashantkumar1982 prashantkumar1982 marked this pull request as ready for review January 30, 2026 22:00
@prashantkumar1982 prashantkumar1982 requested review from a team as code owners January 30, 2026 22:00
@prashantkumar1982 prashantkumar1982 enabled auto-merge (squash) January 30, 2026 22:09
@cl-sonarqube-production
Copy link

cl-sonarqube-production bot commented Jan 30, 2026

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@prashantkumar1982 prashantkumar1982 merged commit cae3b8c into release/2.32.0-cre Jan 30, 2026
207 of 210 checks passed
@prashantkumar1982 prashantkumar1982 mentioned this pull request Jan 30, 2026
Open
@trunk-io
Copy link

trunk-io bot commented Jan 30, 2026

Static Badge   Static Badge   Static Badge   Static Badge

View Full Report ↗︎ ⋅ Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jmank88 jmank88 jmank88 approved these changes

@ChrisAmora ChrisAmora Awaiting requested review from ChrisAmora

@MStreet3 MStreet3 Awaiting requested review from MStreet3

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@prashantkumar1982 @jmank88