# \#versioning

**URL:** https://discourse.julialang.org/tag/versioning/479.md

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

---

## [How do set Julia version in VSCode when using juliaup](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619)

<div class="topic-metadata">

**Author:** [@Torkel](https://discourse.julialang.org/u/Torkel)\
**Replies:** 19\
**Last updated:** [January 15, 2026, 3:29pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619 "2026-01-15T15:29:43Z")

</div>

I am using Juliaup to manage my Julai version. It is now using the 1.10 beta by default. However, for one application, I need to quickly run something in 1.9. I almost exclusively use VSCode. Is there a way, when using …

---

## [Versioninfo not defined in Main](https://discourse.julialang.org/t/versioninfo-not-defined-in-main/123969)

<div class="topic-metadata">

**Author:** [@leespen1](https://discourse.julialang.org/u/leespen1)\
**Replies:** 4\
**Last updated:** [December 20, 2024, 12:22am UTC](https://discourse.julialang.org/t/versioninfo-not-defined-in-main/123969 "2024-12-20T00:22:05Z")

</div>

I was debugging some issues I had using versioninfo() on an HPC, specifically that I would get the following error: ERROR: UndefVarError: \`versioninfo\` not defined in \`Main\` Suggestion: check for spelling errors or miss…

---

## [Why my VSCode extension is not in the latest version?](https://discourse.julialang.org/t/why-my-vscode-extension-is-not-in-the-latest-version/118564)

<div class="topic-metadata">

**Author:** [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Replies:** 2\
**Last updated:** [August 25, 2024, 12:11am UTC](https://discourse.julialang.org/t/why-my-vscode-extension-is-not-in-the-latest-version/118564 "2024-08-25T00:11:19Z")

</div>

I am on Julia v1.10.4 but the VSCode extension version is v1.79.2. I know other people already have version \>v1.100, and that is not pre-release. I sync my VSCode across two devices, one with Linux and another with Wind…

---

## [Determining lower bound of compat statement](https://discourse.julialang.org/t/determining-lower-bound-of-compat-statement/117248)

<div class="topic-metadata">

**Author:** [@bclyons12](https://discourse.julialang.org/u/bclyons12)\
**Replies:** 1\
**Last updated:** [August 19, 2024, 1:45pm UTC](https://discourse.julialang.org/t/determining-lower-bound-of-compat-statement/117248 "2024-08-19T13:45:19Z")

</div>

Is there a way to test the lower bound compatibility of a package systematically, say by doing a binary search to find the lowest version for which tests pass? When adding a new compat entry to a Project.toml, CompatHelp…

---

## [PSA: Add Downgrade CI to Better Check Version Compatibility](https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063)

<div class="topic-metadata">

**Author:** [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Replies:** 35\
**Last updated:** [March 14, 2024, 1:45pm UTC](https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063 "2024-03-14T13:45:53Z")

</div>

A call to all Julia package authors to add Downgrade CI with scripts to copy-paste! This is an article about how to improve testing of package version compatibility and new systems we have adopted in SciML that I would l…

---

## [Questions on the versioning semantics of Julia packages](https://discourse.julialang.org/t/questions-on-the-versioning-semantics-of-julia-packages/109926)

<div class="topic-metadata">

**Author:** [@WuSiren](https://discourse.julialang.org/u/WuSiren)\
**Replies:** 5\
**Last updated:** [February 8, 2024, 4:48pm UTC](https://discourse.julialang.org/t/questions-on-the-versioning-semantics-of-julia-packages/109926 "2024-02-08T16:48:18Z")

</div>

I read this post that tells the rules of Julia package versioning: But didn’t get under what circumstances will the package version string turn from a pre-1.0 form to a post-1.0 form (0.y.z → 1.0.0)? And does Julia’s o…

---

## [Incrementing package version number between releases](https://discourse.julialang.org/t/incrementing-package-version-number-between-releases/106966)

<div class="topic-metadata">

**Author:** [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Replies:** 10\
**Last updated:** [December 2, 2023, 8:18pm UTC](https://discourse.julialang.org/t/incrementing-package-version-number-between-releases/106966 "2023-12-02T20:18:11Z")

</div>

Is there an established best practice for when to bump the version number between releases? Say I just released 1.0.0 and that’s what’s in the HEAD of main in Project.toml. Now I start a branch to develop some feature. I…

---

## [Adding compat entry to stdlib breaks tests on Julia 1.3](https://discourse.julialang.org/t/adding-compat-entry-to-stdlib-breaks-tests-on-julia-1-3/105705)

<div class="topic-metadata">

**Author:** [@jlchan](https://discourse.julialang.org/u/jlchan)\
**Replies:** 10\
**Last updated:** [November 2, 2023, 6:58pm UTC](https://discourse.julialang.org/t/adding-compat-entry-to-stdlib-breaks-tests-on-julia-1-3/105705 "2023-11-02T18:58:33Z")

</div>

I’m trying to register a new package version, and JuliaRegistrator asked me to add a compat entry for LinearAlgebra.jl. I added LinearAlgebra = "1" to my compat entry, but then my Github CI tests for Julia 1.3 fail with …

---

## [Any breaking changes in NLopt v1.0.0?](https://discourse.julialang.org/t/any-breaking-changes-in-nlopt-v1-0-0/102988)

<div class="topic-metadata">

**Author:** [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Replies:** 2\
**Last updated:** [August 20, 2023, 2:05pm UTC](https://discourse.julialang.org/t/any-breaking-changes-in-nlopt-v1-0-0/102988 "2023-08-20T14:05:35Z")

</div>

NLopt v1.0.0 just got tagged (:tada:). See Release v1.0.0 · JuliaOpt/NLopt.jl · GitHub. Were there any breaking changes compared to the previous stable version, v0.6.5? This is not transparent from looking at the commit…

---

## [Anyone fetching UUIDs using LibPQ.jl?](https://discourse.julialang.org/t/anyone-fetching-uuids-using-libpq-jl/89395)

<div class="topic-metadata">

**Author:** [@iamed2](https://discourse.julialang.org/u/iamed2)\
**Replies:** 2\
**Last updated:** [October 27, 2022, 8:40pm UTC](https://discourse.julialang.org/t/anyone-fetching-uuids-using-libpq-jl/89395 "2022-10-27T20:40:26Z")

</div>

I’m introducing support for parsing UUIDs from PostgreSQL in LibPQ.jl and I would like to know if anyone would be negatively impacted by setting UUID as the default type for the PostgreSQL uuid type. This means that if y…

---

## [Jupyter notebooks all use latest version of Julia, even if marked as previous version](https://discourse.julialang.org/t/jupyter-notebooks-all-use-latest-version-of-julia-even-if-marked-as-previous-version/87913)

<div class="topic-metadata">

**Author:** [@Torkel](https://discourse.julialang.org/u/Torkel)\
**Replies:** 4\
**Last updated:** [September 28, 2022, 12:04pm UTC](https://discourse.julialang.org/t/jupyter-notebooks-all-use-latest-version-of-julia-even-if-marked-as-previous-version/87913 "2022-09-28T12:04:59Z")

</div>

I just installed the latest version of Julia (1.8.1). I set it so that is the version that is run when I write “julia” in my terminal (I am on Ubuntu). However, now when I open my previous (1.7.3) Julia notebooks, they …

---

## [New package version not appearing on Juliahub](https://discourse.julialang.org/t/new-package-version-not-appearing-on-juliahub/84989)

<div class="topic-metadata">

**Author:** [@satyabrata\_pal](https://discourse.julialang.org/u/satyabrata_pal)\
**Replies:** 6\
**Last updated:** [July 30, 2022, 7:03am UTC](https://discourse.julialang.org/t/new-package-version-not-appearing-on-juliahub/84989 "2022-07-30T07:03:19Z")

</div>

I had recently registered a new version of my package “Nbdev.jl” - source -GitHub - sapal6/Nbdev.jl: Create Julia packages from Notebooks When I search my package on juliahub, i can see the package’s name and new versio…

---

## [Is there a "correct" way to check if I am running a nightly build of Julia?](https://discourse.julialang.org/t/is-there-a-correct-way-to-check-if-i-am-running-a-nightly-build-of-julia/82754)

<div class="topic-metadata">

**Author:** [@Krastanov](https://discourse.julialang.org/u/Krastanov)\
**Replies:** 0\
**Last updated:** [June 14, 2022, 2:59pm UTC](https://discourse.julialang.org/t/is-there-a-correct-way-to-check-if-i-am-running-a-nightly-build-of-julia/82754 "2022-06-14T14:59:51Z")

</div>

Is there an official way to check if I am running a non-release version of Julia? Any footguns to be aware of if I just do occursin("DEV",string(VERSION))? The reason for this question is that I want to permit certain t…

---

## [Specify a prerelease version in Project.toml compat section?](https://discourse.julialang.org/t/specify-a-prerelease-version-in-project-toml-compat-section/69938)

<div class="topic-metadata">

**Author:** [@Mark\_Nahabedian](https://discourse.julialang.org/u/Mark_Nahabedian)\
**Replies:** 1\
**Last updated:** [October 17, 2021, 8:00pm UTC](https://discourse.julialang.org/t/specify-a-prerelease-version-in-project-toml-compat-section/69938 "2021-10-17T20:00:48Z")

</div>

I have a clone of NativeSVG.jl at https://github.com/MarkNahabedian/NativeSVG.jl. It’s Project.toml file designates it as version = "0.1.0-naha" which parses successfully as a VersionNumber. VersionNumber("0.1.0-nah…

---

## [How to register breaking changes?](https://discourse.julialang.org/t/how-to-register-breaking-changes/69451)

<div class="topic-metadata">

**Author:** [@Johncowk](https://discourse.julialang.org/u/Johncowk)\
**Replies:** 7\
**Last updated:** [October 8, 2021, 10:31pm UTC](https://discourse.julialang.org/t/how-to-register-breaking-changes/69451 "2021-10-08T22:31:21Z")

</div>

I made some breaking changes to one of my package and consequently incremented the version number of 0.1 instead of 0.0.1, but this is not recognized as such by the bot so now my pull request has to be merged manually. W…

---

## [PSA: If your package's version is of the form \`0.y.z\`, please do NOT bump the minor version for new features](https://discourse.julialang.org/t/psa-if-your-packages-version-is-of-the-form-0-y-z-please-do-not-bump-the-minor-version-for-new-features/46570)

<div class="topic-metadata">

**Author:** [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Replies:** 0\
**Last updated:** [September 14, 2020, 3:08am UTC](https://discourse.julialang.org/t/psa-if-your-packages-version-is-of-the-form-0-y-z-please-do-not-bump-the-minor-version-for-new-features/46570 "2020-09-14T03:08:55Z")

</div>

The Julia package manager implements semantic versioning differently for packages that are pre-1.0 versus packages that are post-1.0. For packages that are pre-1.0 (i.e. the package’s version is of the form 0.y.z), we i…

---

## [Version \* does not match other versions](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995)

<div class="topic-metadata">

**Author:** [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Replies:** 8\
**Last updated:** [January 26, 2021, 10:47pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995 "2021-01-26T22:47:11Z")

</div>

I’m using Julia 1.5.3 Trying to run my tests locally, and I get this error about PyCall version conflicts. My own package has a PyCall version dependency of \* whereas some other package (not one of mine) has a PyCall v…

---

## [Release next version of registered packages](https://discourse.julialang.org/t/release-next-version-of-registered-packages/47690)

<div class="topic-metadata">

**Author:** [@iHany](https://discourse.julialang.org/u/iHany)\
**Replies:** 5\
**Last updated:** [October 3, 2020, 12:47pm UTC](https://discourse.julialang.org/t/release-next-version-of-registered-packages/47690 "2020-10-03T12:47:35Z")

</div>

I recently registered a package via Registrator.jl. However, I don’t know how to update and control the version of releases. I’d like to update version (e.g., v0.2.2 for the newest commit), but it looks v0.1.0 in Gener…