<feed xmlns='http://www.w3.org/2005/Atom'>
<title>atuin/.github/workflows/release.yaml, branch main</title>
<subtitle>Turtle. A hard-fork of atuin, focusing on a more minimal feature set</subtitle>
<id>http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/.github/workflows/release.yaml?h=main</id>
<link rel='self' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/.github/workflows/release.yaml?h=main'/>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/'/>
<updated>2024-06-05T12:25:01Z</updated>
<entry>
<title>chore: switch to cargo dist for releases (#2085)</title>
<updated>2024-06-05T12:25:01Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-06-05T12:25:01Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=7ec002ba4476276a4f5a49ed9d3e4b6cf6a53928'/>
<id>urn:sha1:7ec002ba4476276a4f5a49ed9d3e4b6cf6a53928</id>
<content type='text'>
* chore: switch to cargo dist for releases

From https://axo.dev

cargo-dist handles building releases far better than we can, and do so
for several large projects now.

We will need to change our install script to use the cargo-dist
installer.

Historically, we have used the system package manager wherever possible.
Once switched to the new installer, this will no longer be the case. If
the user wishes to use their package manager, and Atuin is maintained
there, then they can choose to do so.

This way, we can ensure that users are running a known build, can easily
uninstall (just delete the atuin dir), easily update, etc. Builds will
use our lockfile, and can have their checksum verified. Later, I'd like
to introduce build signing.

As Axo are focused on release engineering, they will likely have
resolved many more issues than we have - libc versions, etc.

I'm not particularly happy with our response of "just use your package
manager", as many users seem to have difficulty there. It's unclear what
our installer has done, as this behaviour varies massively across
systems. It's also unclear how some package maintainers may have patched
things

I'm hoping that some better release tooling will lead to more confidence
in the process, and therefore more frequent releases.

Uninstall clarity: #111, #372, #640, #1485, #1546, #2049, #1529

* config

* add protobuf

* test build

* use native arm mac

* lol

* add toolchain

* use 1.78, 2vcpu

* nix flake update

* 1.77</content>
</entry>
<entry>
<title>feat: add background daemon (#2006)</title>
<updated>2024-05-08T11:09:04Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-05-08T11:09:04Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=bce0faa1c2dc221b0ff77d2cd647bfb2a48ffa7e'/>
<id>urn:sha1:bce0faa1c2dc221b0ff77d2cd647bfb2a48ffa7e</id>
<content type='text'>
* init daemon crate

* wip

* minimal functioning daemon, needs cleanup for sure

* better errors

* add signal cleanup

* logging

* things

* add sync worker

* move daemon crate

* 30s -&gt; 5mins

* make clippy happy

* fix stuff maybe?

* fmt

* trim packages

* rate limit fix

* more protoc huh

* this makes no sense, why linux why

* can it install literally just curl

* windows in ci is slow, and all the newer things will not work there. disable the daemon feature and it will build

* add daemon feature

* maybe this

* ok wut where is protoc

* try setting protoc

* hm

* try copying protoc

* remove optional

* add cross config

* idk nix

* does nix want this?

* some random pkg I found does this

* uh oh

* hack, be gone!

* update contributing</content>
</entry>
<entry>
<title>fix(ci): release workflow (#1978)</title>
<updated>2024-04-24T15:45:35Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-04-24T15:45:35Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=38ea7706a0ed2929838804db69bda2a53763c97c'/>
<id>urn:sha1:38ea7706a0ed2929838804db69bda2a53763c97c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat(nushell): add nushell completion generation (#1791)</title>
<updated>2024-02-29T11:08:32Z</updated>
<author>
<name>Remmy Cat Stock</name>
<email>3317423+remmycat@users.noreply.github.com</email>
</author>
<published>2024-02-29T11:08:32Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=5f0e6dd3076fe61c3e70898d789f4a7087f53d49'/>
<id>urn:sha1:5f0e6dd3076fe61c3e70898d789f4a7087f53d49</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chore(ci): use github m1 for release builds (#1658)</title>
<updated>2024-01-30T18:29:13Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-01-30T18:29:13Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=f6b541dbedcc3ae719dd3d1d0f889f2ca8e0f7d6'/>
<id>urn:sha1:f6b541dbedcc3ae719dd3d1d0f889f2ca8e0f7d6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: disable musl deb building (#1525)</title>
<updated>2024-01-09T11:49:00Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-01-09T11:49:00Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=2b94f05735fe83db741370078ebfb44fa92b6907'/>
<id>urn:sha1:2b94f05735fe83db741370078ebfb44fa92b6907</id>
<content type='text'>
It never worked, and broke release building. I don't think we need musl
debs, but if so ensure they don't break install scripts

Resolve #1500</content>
</entry>
<entry>
<title>Fix cargo deb usage (#1337)</title>
<updated>2023-10-26T15:13:54Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2023-10-26T15:13:54Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=b7adf1d797f43d8547751bf7923db66c2d01c107'/>
<id>urn:sha1:b7adf1d797f43d8547751bf7923db66c2d01c107</id>
<content type='text'>
v2.0.0 of cargo deb added the revision number. I'd rather not change the
output name of our file, so force cargo-deb to stick to the "old"
behaviour</content>
</entry>
<entry>
<title>Add self hosted runner (#1133)</title>
<updated>2023-07-30T22:16:01Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2023-07-30T22:16:01Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=43afb2d702b2508fc4c9d9e99d4dd56f786706ac'/>
<id>urn:sha1:43afb2d702b2508fc4c9d9e99d4dd56f786706ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>update release.yaml add RUSTFLAGS, add qemu-user, add QEMU_PREFIX before gen-completions (#872)</title>
<updated>2023-06-13T07:54:27Z</updated>
<author>
<name>mmx</name>
<email>github@m2nx.com</email>
</author>
<published>2023-06-13T07:54:27Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=dea6898f2d7e4bd4f5f1e65c3379d4766e57963d'/>
<id>urn:sha1:dea6898f2d7e4bd4f5f1e65c3379d4766e57963d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Upload tar before building deb (#898)</title>
<updated>2023-04-19T08:04:31Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2023-04-19T08:04:31Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=beadc959269bd936d5d3628b6261871fd6ce6f1c'/>
<id>urn:sha1:beadc959269bd936d5d3628b6261871fd6ce6f1c</id>
<content type='text'>
</content>
</entry>
</feed>
