You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+35-15Lines changed: 35 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,33 +2,53 @@ Pkg v1.8 Release Notes
2
2
======================
3
3
4
4
- New `⌃` and `⌅` indicators beside packages in `pkg> status` that have new versions available.
5
-
`⌅` indicates when new versions cannot be installed.
5
+
`⌅` indicates when new versions cannot be installed ([#2906]).
6
6
- New `outdated::Bool` kwarg to `Pkg.status` (`--outdated` or `-o` in the REPL mode) to show
7
-
information about packages not at the latest version.
7
+
information about packages not at the latest version ([#2284]).
8
8
- New `compat::Bool` kwarg to `Pkg.status` (`--compat` or `-c` in the REPL mode) to show any [compat]
9
-
entries in the Project.toml.
9
+
entries in the Project.toml ([#2702]).
10
10
- New `pkg> compat` (and `Pkg.compat`) mode for setting Project compat entries. Provides an interactive editor
11
11
via `pkg> compat`, or direct entry manipulation via `pkg> Foo 0.4,0.5` which can load current entries via tab-completion.
12
-
i.e. `pkg> compat Fo<TAB>` autocompletes to `pkg> Foo 0.4,0.5` so that the existing entry can be edited.
13
-
- Pkg now only tries to download packages from the package server in case the
14
-
server tracks a registry that contains the package.
12
+
i.e. `pkg> compat Fo<TAB>` autocompletes to `pkg> Foo 0.4,0.5` so that the existing entry can be edited ([#2702]).
13
+
- Pkg now only tries to download packages from the package server in case the server tracks a registry that contains
14
+
the package ([#2689]).
15
15
-`Pkg.instantiate` will now warn when a Project.toml is out of sync with a Manifest.toml. It does this by storing a hash
16
16
of the project deps and compat entries (other fields are ignored) in the manifest when it is resolved, so that any change
17
-
to the Project.toml deps or compat entries without a re-resolve can be detected.
17
+
to the Project.toml deps or compat entries without a re-resolve can be detected ([#2815]).
18
+
- If `pkg> add` cannot find a package with the provided name it will now suggest similarly named packages that can be added ([#2985]).
19
+
- The julia version stored in the manifest no longer includes the build number i.e. master will now record as `1.9.0-DEV` ([#2995]).
20
+
- Interrupting a `pkg> test` will now be caught more reliably and exit back to the REPL gracefully ([#2933]).
18
21
19
22
Pkg v1.7 Release Notes
20
23
======================
21
24
22
25
- The format of the `Manifest.toml` file have changed. New manifests will use
23
-
the new format while old manifest will have their existing format in place.
24
-
Julia 1.6.2 is compatible with the new format.
26
+
the new format while old manifest will have their existing format in place ([#2580]).
27
+
Julia 1.6.2 is compatible with the new format ([#2561]).
25
28
- Registries downloaded from the Pkg Server (not git) are no longer uncompressed into files but instead read directly from the compressed tarball into memory. This improves performance on
26
-
filesystems which do not handle a large number of files well. To turn this feature off, set the environment variable `JULIA_PKG_UNPACK_REGISTRY=true`.
29
+
filesystems which do not handle a large number of files well. To turn this feature off, set the environment variable `JULIA_PKG_UNPACK_REGISTRY=true` ([#2431]).
27
30
- It is now possible to use an external `git` executable instead of the default libgit2 library for
28
-
the downloads that happen via the Git protocol by setting the environment variable `JULIA_PKG_USE_CLI_GIT=true`.
31
+
the downloads that happen via the Git protocol by setting the environment variable `JULIA_PKG_USE_CLI_GIT=true` ([#2448]).
29
32
- Registries downloaded from the Pkg Server (not git) is now assumed to be immutable. Manual changes to their files might not be picked up by a running Pkg session.
30
33
- The number of packags precompiled in parallel are now limited to 16 unless the
31
-
environment variable `JULIA_NUM_PRECOMPILE_TASKS` is set.
32
-
- Adding packages by folder name in the REPL mode now requires a prepending a `./` to the folder name package folder is in the current folder, e.g. `add ./Package` is required instead of `add Pacakge`. This is to avoid confusion between the package name `Package` and the local directory `Package`.
33
-
-`rm`, `pin`, and `free` now support the `--all` option, and the api variants gain the `all_pkgs::Bool` kwarg, to perform the operation on all packages within the project or manifest, depending on the mode of the operation.
34
-
- The `mode` keyword for `PackageSpec` has been removed.
34
+
environment variable `JULIA_NUM_PRECOMPILE_TASKS` is set ([#2552]).
35
+
- Adding packages by folder name in the REPL mode now requires a prepending a `./` to the folder name package folder is in the current folder, e.g. `add ./Package` is required instead of `add Package`. This is to avoid confusion between the package name `Package` and the local directory `Package`.
36
+
-`rm`, `pin`, and `free` now support the `--all` option, and the api variants gain the `all_pkgs::Bool` kwarg, to perform the operation on all packages within the project or manifest, depending on the mode of the operation ([#2432]).
37
+
- The `mode` keyword for `PackageSpec` has been removed ([#2454]).
Copy file name to clipboardExpand all lines: docs/src/creating-packages.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -309,5 +309,5 @@ To support the various usecases in the Julia package ecosystem, the Pkg develope
309
309
*[`Preferences.jl`](https://github.com/JuliaPackaging/Preferences.jl) allows packages to read and write preferences to the top-level `Project.toml`.
310
310
These preferences can be read at runtime or compile-time, to enable or disable different aspects of package behavior.
311
311
Packages previously would write out files to their own package directories to record options set by the user or environment, but this is highly discouraged now that `Preferences` is available.
0 commit comments