NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #2564 by repository stars
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 7 months
Nearly every release is documented
notes for 5 of 5 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
13 releases · first in 2023
One column per quarter.
Nothing published for this version
Nothing published for this version
This is a minor hotfix release that addresses the Windows compatibility issue introduced in Linsk v0.2.1.
This is a minor hotfix release that addresses the Windows compatibility issue introduced in Linsk v0.2.1.
Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.2.2.txt.sig linsk_sha256_v0.2.2.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <alexandersadovskyi7@protonmail.com>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.2.2.txt) and compare the checksums. You can generate a checksum by executing this command:
sha256sum <file path>
Nothing published for this version
This is a minor maintenance release, predominantly containing the fix for compatibility issues for Intel-based macOS machines ( darwin/amd64 ).
This is a minor maintenance release, predominantly containing the fix for compatibility issues for Intel-based macOS machines (darwin/amd64).
Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.2.1.txt.sig linsk_sha256_v0.2.1.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <alexandersadovskyi7@protonmail.com>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.2.1.txt) and compare the checksums. You can generate a checksum by executing this command:
sha256sum <file path>
Nothing published for this version
Linsk v0.2.0 addresses the Faulty raw device block size detection serious bug . Versions below v0.2.0 are considered obsolete UNLESS :
Linsk v0.2.0 addresses the Faulty raw device block size detection serious bug. Versions below v0.2.0 are considered obsolete UNLESS:
Please see serious-bug-disclosures/README.md@master for more information.
The exact list of changes is as follows:
linsk run.linsk run. Falls back to the default of vdb (the entire drive) if none is specified.--luks-container flag.Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.2.0.txt.sig linsk_sha256_v0.2.0.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <alexandersadovskyi7@protonmail.com>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.2.0.txt) and compare the checksums. You can generate a checksum by executing this command:
sha256sum <file path>
Nothing published for this version
Nothing published for this version
This release is susceptible to the Faulty raw device block size detection serious bug .
This release is susceptible to the Faulty raw device block size detection serious bug.
Linsk versions below v0.2.0 are considered obsolete UNLESS:
More information: serious-bug-disclosures/README.md
This is a minor maintenance release containing insignificant fixes following the initial release.
The exact list of changes is as follows:
qemu-system stderr passthrough when running with --vm-debug option.linsk version showing v0.0.0.Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.1.1.txt.sig linsk_sha256_v0.1.1.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <alexandersadovskyi7@protonmail.com>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.1.1.txt) and compare the checksums. You can generate a checksum by executing this command:
sha256sum <file path>
Nothing published for this version
Nothing published for this version
This release is susceptible to the Faulty raw device block size detection serious bug .
This release is susceptible to the Faulty raw device block size detection serious bug.
Linsk versions below v0.2.0 are considered obsolete UNLESS:
More information: serious-bug-disclosures/README.md
This is the initial release of Linsk.
Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing the following:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.1.0.txt.sig linsk_sha256_v0.1.0.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <alexandersadovskyi7@protonmail.com>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.1.0.txt) and compare the checksums. You can generate a checksum by executing the following command:
sha256sum <file path>
Your coding agent can read these notes before it upgrades. Set up the MCP server →