# \#opam-repository

**URL:** https://discuss.ocaml.org/tag/opam-repository/591.md

[Latest](https://discuss.ocaml.org/latest.md) · [Categories](https://discuss.ocaml.org/categories.md) · [Tags](https://discuss.ocaml.org/tags.md)

---

## [Request for comments: What to do with opam packages that have known security vulnerabilities](https://discuss.ocaml.org/t/request-for-comments-what-to-do-with-opam-packages-that-have-known-security-vulnerabilities/18087)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 23\
**Last updated:** [May 26, 2026, 7:49am UTC](https://discuss.ocaml.org/t/request-for-comments-what-to-do-with-opam-packages-that-have-known-security-vulnerabilities/18087 "2026-05-26T07:49:11Z")

</div>

Dear everyone, we (the OCaml security) team is curious what the practice should be for opam packages that have known security vulnerabilities? One way is to mark them with available: false in the opam-repository, which…

---

## [\[archival\] \[ann\] Raising the OCaml lower bound to 4.11.0 for opam-repository](https://discuss.ocaml.org/t/archival-ann-raising-the-ocaml-lower-bound-to-4-11-0-for-opam-repository/17965)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 30\
**Last updated:** [May 18, 2026, 8:44am UTC](https://discuss.ocaml.org/t/archival-ann-raising-the-ocaml-lower-bound-to-4-11-0-for-opam-repository/17965 "2026-05-18T08:44:21Z")

</div>

Based on the discussion in https://discuss.ocaml.org/t/dropping-some-intermediate-ocaml-versions-from-ci/ I ran the archive-opam tool with the ocaml-lower-bound set to 4.11.0. As a result, the following packages would b…

---

## [Opam repository archival, next run (scheduled 2026-01-01)](https://discuss.ocaml.org/t/opam-repository-archival-next-run-scheduled-2026-01-01/17587)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 9\
**Last updated:** [April 8, 2026, 6:56pm UTC](https://discuss.ocaml.org/t/opam-repository-archival-next-run-scheduled-2026-01-01/17587 "2026-04-08T18:56:35Z")

</div>

Dear everyone, we did another run of the archival based on the x-maintenance-intent of opam packages. The run was using opam-repository at commit d684c896eb6f7e6030d6ee65338d9db22a612f01 (Dec 9th, 20:00:00 CET). The to…

---

## [\[BLOG\] Opam 104: Sharing Your Code, by OCamlPro](https://discuss.ocaml.org/t/blog-opam-104-sharing-your-code-by-ocamlpro/17710)

<div class="topic-metadata">

**Author:** [@OCamlPro](https://discuss.ocaml.org/u/OCamlPro)\
**Replies:** 6\
**Last updated:** [January 26, 2026, 4:47pm UTC](https://discuss.ocaml.org/t/blog-opam-104-sharing-your-code-by-ocamlpro/17710 "2026-01-26T16:47:03Z")

</div>

Greetings Cameleers, We’ve just released a new blog post: Opam 104: Sharing Your Code This article is the final entry in our opam deep-dives series, and it focuses on a key step in every OCaml project’s life: making it…

---

## [Opam repository archival, phase 3](https://discuss.ocaml.org/t/opam-repository-archival-phase-3/16748)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 21\
**Last updated:** [December 10, 2025, 11:12am UTC](https://discuss.ocaml.org/t/opam-repository-archival-phase-3/16748 "2025-12-10T11:12:54Z")

</div>

Dear everyone, the phase 3 of the opam repository archival (taking the x-maintenance-intent into account) is now ready. We ran on 30th of May the maintenance-intent filter, which resulted in 6463 candidates of which we’…

---

## [Opam-repository, signed! conex is in beta now :)](https://discuss.ocaml.org/t/opam-repository-signed-conex-is-in-beta-now/17461)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 7\
**Last updated:** [November 11, 2025, 5:19pm UTC](https://discuss.ocaml.org/t/opam-repository-signed-conex-is-in-beta-now/17461 "2025-11-11T17:19:57Z")

</div>

Dear everyone, we’re proud to announce that conex, in an initial version, is now live! You can receive signed updates of the opam-repository. A quick guide: To setup opam with conex on your machine, you need to install…

---

## [\[ANN\] opam-publish 2.7.0](https://discuss.ocaml.org/t/ann-opam-publish-2-7-0/17358)

<div class="topic-metadata">

**Author:** [@kit-ty-kate](https://discuss.ocaml.org/u/kit-ty-kate)\
**Replies:** 0\
**Last updated:** [October 7, 2025, 2:37pm UTC](https://discuss.ocaml.org/t/ann-opam-publish-2-7-0/17358 "2025-10-07T14:37:03Z")

</div>

Hi everyone, We are happy to announce the release of opam-publish 2.7.0 (and 2.6.0), which together brought the ability to more easily publish your releases automatically, thanks to @filipeom: A new OPAM\_PUBLISH\_GH\_T…

---

## [Opam repository package versioning policy?](https://discuss.ocaml.org/t/opam-repository-package-versioning-policy/16796)

<div class="topic-metadata">

**Author:** [@yawaramin](https://discuss.ocaml.org/u/yawaramin)\
**Replies:** 5\
**Last updated:** [June 19, 2025, 1:43am UTC](https://discuss.ocaml.org/t/opam-repository-package-versioning-policy/16796 "2025-06-19T01:43:18Z")

</div>

I checked the existing policies here: opam-repository/governance/policies at master · ocaml/opam-repository · GitHub However I could not find anything that talks explicitly about a package versioning policy ie what vers…

---

## [Opinion: Is it time to stop testing with opam \< 2.2](https://discuss.ocaml.org/t/opinion-is-it-time-to-stop-testing-with-opam-2-2/16723)

<div class="topic-metadata">

**Author:** [@shonfeder](https://discuss.ocaml.org/u/shonfeder)\
**Replies:** 3\
**Last updated:** [May 29, 2025, 4:39pm UTC](https://discuss.ocaml.org/t/opinion-is-it-time-to-stop-testing-with-opam-2-2/16723 "2025-05-29T16:39:25Z")

</div>

---

## [Call for Volunteers to Help Maintain the Opam-Repository](https://discuss.ocaml.org/t/call-for-volunteers-to-help-maintain-the-opam-repository/16476)

<div class="topic-metadata">

**Author:** [@shonfeder](https://discuss.ocaml.org/u/shonfeder)\
**Replies:** 0\
**Last updated:** [April 11, 2025, 1:47pm UTC](https://discuss.ocaml.org/t/call-for-volunteers-to-help-maintain-the-opam-repository/16476 "2025-04-11T13:47:25Z")

</div>

The opam-repository needs your help! :camel::heart: tl;dr: Want to grow your OCaml connections and expertise while supporting a pillar of the ecosystem? Then join us as an opam-repository maintainer by commenting on the …

---

## [OPAM-CI Windows runs: how do I see the logs?](https://discuss.ocaml.org/t/opam-ci-windows-runs-how-do-i-see-the-logs/16334)

<div class="topic-metadata">

**Author:** [@Chet\_Murthy](https://discuss.ocaml.org/u/Chet_Murthy)\
**Replies:** 4\
**Last updated:** [March 20, 2025, 7:23pm UTC](https://discuss.ocaml.org/t/opam-ci-windows-runs-how-do-i-see-the-logs/16334 "2025-03-20T19:23:45Z")

</div>

I’m trying (it’s trying, but I’m trying) to get various packages working on Windows, and to do so, I need to verify things like “they got installed with the correct names” since I don’t run Windows anywhere and never hav…

---

## [Opam repository archival - next phase delayed](https://discuss.ocaml.org/t/opam-repository-archival-next-phase-delayed/16203)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 0\
**Last updated:** [February 28, 2025, 10:33am UTC](https://discuss.ocaml.org/t/opam-repository-archival-next-phase-delayed/16203 "2025-02-28T10:33:08Z")

</div>

Dear everyone, sorry for the silence – the phase 3 of the opam repository archival (taking the x-maintenance-intent into account) has to be delayed by (tentatively) one month. The reason is that our tooling is not ready…

---

## [Opam repository archival, phase 2 - OCaml 4.08 is the lower bound](https://discuss.ocaml.org/t/opam-repository-archival-phase-2-ocaml-4-08-is-the-lower-bound/15965)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 21\
**Last updated:** [February 26, 2025, 2:13pm UTC](https://discuss.ocaml.org/t/opam-repository-archival-phase-2-ocaml-4-08-is-the-lower-bound/15965 "2025-02-26T14:13:59Z")

</div>

It is my pleasure to announce below the list of opam packages that will move to the opam-repository-archive on February 1st 2025. In total there are 5855 opam files scheduled for being moved within 1218 unique packages. …

---

## [Opam repository archive - clarification of the opam fields](https://discuss.ocaml.org/t/opam-repository-archive-clarification-of-the-opam-fields/16050)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 0\
**Last updated:** [January 28, 2025, 5:14pm UTC](https://discuss.ocaml.org/t/opam-repository-archive-clarification-of-the-opam-fields/16050 "2025-01-28T17:14:44Z")

</div>

Dear everyone, we had further discussions about the semantics of x-maintenance-intent, and hope to clarify in this post. Also, we adapted the policy which is in the opam-repository git repository: opam-repository/govern…

---

## [Opam repository archival, Phase 1: unavailable packages](https://discuss.ocaml.org/t/opam-repository-archival-phase-1-unavailable-packages/15797)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 6\
**Last updated:** [January 1, 2025, 7:12pm UTC](https://discuss.ocaml.org/t/opam-repository-archival-phase-1-unavailable-packages/15797 "2025-01-01T19:12:15Z")

</div>

It is my pleasure to announce below the list of opam packages that will move to the opam-repository-archive on January 1st 2025. In total there are 4170 opam files scheduled for being moved within 561 unique packages. Th…

---

## [Proposed Package Archiving Policy for the opam Repository](https://discuss.ocaml.org/t/proposed-package-archiving-policy-for-the-opam-repository/15713)

<div class="topic-metadata">

**Author:** [@hannes](https://discuss.ocaml.org/u/hannes)\
**Replies:** 5\
**Last updated:** [December 12, 2024, 7:45pm UTC](https://discuss.ocaml.org/t/proposed-package-archiving-policy-for-the-opam-repository/15713 "2024-12-12T19:45:03Z")

</div>

Dear everyone, it is my please to announce the proposed package archiving policy in the name of the opam-repository maintainers. Context The opam repository differs from nearly all other programming-language-centric pa…

---

## [Opam-repository: Updated documentation, retirement and call for maintainers](https://discuss.ocaml.org/t/opam-repository-updated-documentation-retirement-and-call-for-maintainers/14325)

<div class="topic-metadata">

**Author:** [@kit-ty-kate](https://discuss.ocaml.org/u/kit-ty-kate)\
**Replies:** 8\
**Last updated:** [May 14, 2024, 6:25am UTC](https://discuss.ocaml.org/t/opam-repository-updated-documentation-retirement-and-call-for-maintainers/14325 "2024-05-14T06:25:11Z")

</div>

Hi everyone, After having been maintainer of opam-repository for the past 6 and half years, I’m publicly announcing my retirement from it, to focus on opam itself. This change has been more or less already in effect sin…

---

## [Discussions on the future of the opam repository](https://discuss.ocaml.org/t/discussions-on-the-future-of-the-opam-repository/13898)

<div class="topic-metadata">

**Author:** [@raphael-proust](https://discuss.ocaml.org/u/raphael-proust)\
**Replies:** 11\
**Last updated:** [March 18, 2024, 2:05pm UTC](https://discuss.ocaml.org/t/discussions-on-the-future-of-the-opam-repository/13898 "2024-03-18T14:05:09Z")

</div>

The default opam repository has been getting larger and larger with an ever increasing number of packages. This is somewhat of a good sign for the active community of OCaml developers. But it is also a challenge for its …

---

## [Call for new opam-repository maintainers](https://discuss.ocaml.org/t/call-for-new-opam-repository-maintainers/12041)

<div class="topic-metadata">

**Author:** [@kit-ty-kate](https://discuss.ocaml.org/u/kit-ty-kate)\
**Replies:** 10\
**Last updated:** [December 2, 2023, 7:47am UTC](https://discuss.ocaml.org/t/call-for-new-opam-repository-maintainers/12041 "2023-12-02T07:47:57Z")

</div>

Come and help maintenance of the opam-repository! opam-repository is the official store of package descriptions for the OCaml ecosystem. It allows everyone to easily install whatever dependency their project might need.…
