Skip to content

add OSEC-2026-01#17

Merged
hannesm merged 2 commits intomainfrom
2026-01
Feb 17, 2026
Merged

add OSEC-2026-01#17
hannesm merged 2 commits intomainfrom
2026-01

Conversation

@hannesm
Copy link
Member

@hannesm hannesm commented Feb 17, 2026

Happy to hear your feedback @nojb @xavierleroy @gasche @Octachron @OlivierNicole @yomimono @edwintorok @JustinTimperio

The two git commits where it is fixed are the 4.14 and 5.4 branch (5.5 and trunk will follow once they are merged)

Copy link

@xavierleroy xavierleroy left a comment

Choose a reason for hiding this comment

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

Looks very good to me. Thank you!

@edwintorok
Copy link
Collaborator

The CI doesn't like something about the way the fixed version is declared.

Copy link
Collaborator

@nojb nojb left a comment

Choose a reason for hiding this comment

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

LGTM

Thanks!

@hannesm
Copy link
Member Author

hannesm commented Feb 17, 2026

The events / fixed: unfortunately git (and osv-schema) doesn't allow to include the branch name as far as I can tell. (and whatever you put after git needs to be something git clone can deal with -- i.e. we can't use the nice opam git-urls with branch names.

Copy link

@OlivierNicole OlivierNicole left a comment

Choose a reason for hiding this comment

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

LGTM

@hannesm hannesm merged commit f3dd6fc into main Feb 17, 2026
2 checks passed
@hannesm hannesm deleted the 2026-01 branch February 17, 2026 14:07
@hannesm
Copy link
Member Author

hannesm commented Feb 17, 2026

Merging, we can always adjust this advisory.

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.

5 participants