# \#manifest

**URL:** https://discourse.julialang.org/tag/manifest/1125.md

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

---

## [Restricting the version of an indirect dependency](https://discourse.julialang.org/t/restricting-the-version-of-an-indirect-dependency/138971)

<div class="topic-metadata">

**Author:** [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Replies:** 9\
**Last updated:** [August 21, 2026, 9:30pm UTC](https://discourse.julialang.org/t/restricting-the-version-of-an-indirect-dependency/138971 "2026-08-21T21:30:31Z")

</div>

The HTTP package is not in my project file, but I would like to restrict its version and upgrade everything else. I have not been able to find a direct way of doing this, so I upgraded everything, then added it to my pro…

---

## [Keeping local Manifest.toml's up to date](https://discourse.julialang.org/t/keeping-local-manifest-tomls-up-to-date/130694)

<div class="topic-metadata">

**Author:** [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Replies:** 9\
**Last updated:** [July 18, 2025, 7:50am UTC](https://discourse.julialang.org/t/keeping-local-manifest-tomls-up-to-date/130694 "2025-07-18T07:50:05Z")

</div>

Generally, I do not commit Manifest.toml, docs/Manifest.toml and test/Manifest.toml (where applicable) to git repositories for packages. However, as a result, sometimes these become out of date for local clones of packa…

---

## [Version-named manifests by default?](https://discourse.julialang.org/t/version-named-manifests-by-default/123618)

<div class="topic-metadata">

**Author:** [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Replies:** 10\
**Last updated:** [July 7, 2025, 4:55am UTC](https://discourse.julialang.org/t/version-named-manifests-by-default/123618 "2025-07-07T04:55:45Z")

</div>

Julia 1.11 supports versioning by manifests, but one has first to manually rename the manifest to use this feature. Should not all newly created manifests be created with the versioned name?

---

## [Incorrect manifest after adding package as dependency that has forked package as dependency](https://discourse.julialang.org/t/incorrect-manifest-after-adding-package-as-dependency-that-has-forked-package-as-dependency/129435)

<div class="topic-metadata">

**Author:** [@KSepetanc](https://discourse.julialang.org/u/KSepetanc)\
**Replies:** 6\
**Last updated:** [May 29, 2025, 5:41pm UTC](https://discourse.julialang.org/t/incorrect-manifest-after-adding-package-as-dependency-that-has-forked-package-as-dependency/129435 "2025-05-29T17:41:43Z")

</div>

What I am doing is creating a custom package. In that package I add forked package as dependency and resulting manifest is correct (so my package has both manifest.toml and project.toml). However, once I add my package t…

---

## [About checking a package/library \`Manifest.toml\` into control version (again)](https://discourse.julialang.org/t/about-checking-a-package-library-manifest-toml-into-control-version-again/127490)

<div class="topic-metadata">

**Author:** [@iago-lito](https://discourse.julialang.org/u/iago-lito)\
**Replies:** 22\
**Last updated:** [May 13, 2025, 12:26pm UTC](https://discourse.julialang.org/t/about-checking-a-package-library-manifest-toml-into-control-version-again/127490 "2025-05-13T12:26:17Z")

</div>

Hello @Julia, From what I understand here and there (but really anywhere), there is almost dogmatic community consensus that Manifest.toml files may be checked into version control for end applications, but certainly no…

---

## [Diff between two Manifest.toml files](https://discourse.julialang.org/t/diff-between-two-manifest-toml-files/121503)

<div class="topic-metadata">

**Author:** [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Replies:** 0\
**Last updated:** [October 20, 2024, 2:01pm UTC](https://discourse.julialang.org/t/diff-between-two-manifest-toml-files/121503 "2024-10-20T14:01:16Z")

</div>

What’s a recommended way to compare and find all the differences between two Manifest.toml files ? I have used plain text diff (e.g. as implemented in vscode) and it seems to work fine. But I think the success of this a…

---

## [What does manifest\_usage.toml file do?](https://discourse.julialang.org/t/what-does-manifest-usage-toml-file-do/105633)

<div class="topic-metadata">

**Author:** [@math\_opt](https://discourse.julialang.org/u/math_opt)\
**Replies:** 6\
**Last updated:** [November 1, 2023, 7:39pm UTC](https://discourse.julialang.org/t/what-does-manifest-usage-toml-file-do/105633 "2023-11-01T19:39:12Z")

</div>

As the title says, what’s the purpose of manifest\_usage.toml? I have a Julia project that has its own project.toml and manifest.toml. When I try to test this project, I sometimes encounter an error that says: Activatin…

---

## [Pkg.upgrade\_manifest errors if the manifest doesn't need upgrading](https://discourse.julialang.org/t/pkg-upgrade-manifest-errors-if-the-manifest-doesnt-need-upgrading/83320)

<div class="topic-metadata">

**Author:** [@Mark\_Nahabedian](https://discourse.julialang.org/u/Mark_Nahabedian)\
**Replies:** 2\
**Last updated:** [March 1, 2023, 5:51am UTC](https://discourse.julialang.org/t/pkg-upgrade-manifest-errors-if-the-manifest-doesnt-need-upgrading/83320 "2023-03-01T05:51:47Z")

</div>

Why is this an error rather than a no-op or warning? Pkg.upgrade\_manifest()' ERROR: Format of manifest file at \`C:\\Users\\Mark Nahabedian\\NahaJuliaLib.jl\\Manifest.toml\` already up to date: manifest\_format == 2.0.0 Stackt…

---

## [ERROR: expected package \`CSV\` to exist in the manifest](https://discourse.julialang.org/t/error-expected-package-csv-to-exist-in-the-manifest/90227)

<div class="topic-metadata">

**Author:** [@clarakoehne](https://discourse.julialang.org/u/clarakoehne)\
**Replies:** 2\
**Last updated:** [November 14, 2022, 2:27pm UTC](https://discourse.julialang.org/t/error-expected-package-csv-to-exist-in-the-manifest/90227 "2022-11-14T14:27:20Z")

</div>

Hello everyone! I am getting a very strange error when I try to run my Julia program. It looks as follows: ERROR: expected package \`CSV \[336ed68f\]\` to exist in the manifest (use \`resolve\` to populate the manifest) Stack…

---

## [The following package names could not be resolved: in manifest but not in project](https://discourse.julialang.org/t/the-following-package-names-could-not-be-resolved-in-manifest-but-not-in-project/86509)

<div class="topic-metadata">

**Author:** [@Xavier\_Gonzalez](https://discourse.julialang.org/u/Xavier_Gonzalez)\
**Replies:** 1\
**Last updated:** [August 29, 2022, 6:42pm UTC](https://discourse.julialang.org/t/the-following-package-names-could-not-be-resolved-in-manifest-but-not-in-project/86509 "2022-08-29T18:42:05Z")

</div>

I am getting weird errors with ChainRules in Julia 1.8 To try to fix the problem, I went into the package manager for my project, and tried both rm ChainRules and rm Zygote. Both times I got the following error message: …