Releases: GitoxideLabs/gitoxide
gix-refspec v0.21.1
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-ref v0.40.1
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-quote v0.4.10
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-protocol v0.43.1
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-prompt v0.8.2
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-pathspec v0.5.1
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-path v0.10.3
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 3 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-packetline v0.17.2
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-packetline-blocking v0.17.2
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-pack v0.46.1
Chore
-
change
rust-versionmanifest field back to 1.65.
They didn't actually need to be higher to work, and changing them
unecessarily can break downstream CI.Let's keep this value as low as possible, and only increase it when
more recent features are actually used.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages