logos-messaging-go/flake.lock

{
  "nodes": {
    "nixpkgs": {
      "locked": {
        "lastModified": 1717159533,
        "narHash": "sha256-oamiKNfr2MS6yH64rUn99mIZjc45nGJlj9eGth/3Xuw=",
        "owner": "NixOS",
        "repo": "nixpkgs",
        "rev": "a62e6edd6d5e1fa0329b8653c801147986f8d446",
        "type": "github"
      },
      "original": {
        "owner": "NixOS",
        "ref": "nixos-23.11",
        "repo": "nixpkgs",
        "type": "github"
      }
    },
    "root": {
      "inputs": {
        "nixpkgs": "nixpkgs"
      }
    }
  },
  "root": "root",
  "version": 7
}
nix: add Nix flake to build node and library This way we can build node or the library locally using: ```sh nix build nix build .#node nix build .#library ``` Or just start a shell with Go `1.19.x` using: ``` nix develop ``` Which simply has the same environment as the build shell for the node. One known snag is that there is currently no simple way to keep `vendorSha256` updated to match the contents of `go.mod` and `go.sum`. For more details see: https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8 One way around this would be to have our own `vendor` folder, but that's also a pretty ugly solution that requires manual updating. Resolves: https://github.com/waku-org/go-waku/issues/256 Signed-off-by: Jakub Sokołowski <jakub@status.im> 2022-06-03 18:59:21 +02:00			`{`
			`"nodes": {`
			`"nixpkgs": {`
			`"locked": {`
chore: upgrade to go1.21 (#1091) 2024-06-04 18:46:28 -04:00			`"lastModified": 1717159533,`
			`"narHash": "sha256-oamiKNfr2MS6yH64rUn99mIZjc45nGJlj9eGth/3Xuw=",`
nix: add Nix flake to build node and library This way we can build node or the library locally using: ```sh nix build nix build .#node nix build .#library ``` Or just start a shell with Go `1.19.x` using: ``` nix develop ``` Which simply has the same environment as the build shell for the node. One known snag is that there is currently no simple way to keep `vendorSha256` updated to match the contents of `go.mod` and `go.sum`. For more details see: https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8 One way around this would be to have our own `vendor` folder, but that's also a pretty ugly solution that requires manual updating. Resolves: https://github.com/waku-org/go-waku/issues/256 Signed-off-by: Jakub Sokołowski <jakub@status.im> 2022-06-03 18:59:21 +02:00			`"owner": "NixOS",`
			`"repo": "nixpkgs",`
chore: upgrade to go1.21 (#1091) 2024-06-04 18:46:28 -04:00			`"rev": "a62e6edd6d5e1fa0329b8653c801147986f8d446",`
nix: add Nix flake to build node and library This way we can build node or the library locally using: ```sh nix build nix build .#node nix build .#library ``` Or just start a shell with Go `1.19.x` using: ``` nix develop ``` Which simply has the same environment as the build shell for the node. One known snag is that there is currently no simple way to keep `vendorSha256` updated to match the contents of `go.mod` and `go.sum`. For more details see: https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8 One way around this would be to have our own `vendor` folder, but that's also a pretty ugly solution that requires manual updating. Resolves: https://github.com/waku-org/go-waku/issues/256 Signed-off-by: Jakub Sokołowski <jakub@status.im> 2022-06-03 18:59:21 +02:00			`"type": "github"`
			`},`
			`"original": {`
			`"owner": "NixOS",`
chore: upgrade to go1.21 (#1091) 2024-06-04 18:46:28 -04:00			`"ref": "nixos-23.11",`
nix: add Nix flake to build node and library This way we can build node or the library locally using: ```sh nix build nix build .#node nix build .#library ``` Or just start a shell with Go `1.19.x` using: ``` nix develop ``` Which simply has the same environment as the build shell for the node. One known snag is that there is currently no simple way to keep `vendorSha256` updated to match the contents of `go.mod` and `go.sum`. For more details see: https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8 One way around this would be to have our own `vendor` folder, but that's also a pretty ugly solution that requires manual updating. Resolves: https://github.com/waku-org/go-waku/issues/256 Signed-off-by: Jakub Sokołowski <jakub@status.im> 2022-06-03 18:59:21 +02:00			`"repo": "nixpkgs",`
			`"type": "github"`
			`}`
			`},`
			`"root": {`
			`"inputs": {`
			`"nixpkgs": "nixpkgs"`
			`}`
			`}`
			`},`
			`"root": "root",`
			`"version": 7`
			`}`