34 Commits

Author SHA1 Message Date
Luis Quiñones
401d4dc83b ci(update): more simple release notes for twilight tags (#93) 2025-08-17 19:26:07 -05:00
Luis Quiñones
3693c02790 ci(zen-update): rebase beta branch from main when needed (#85)
Related to https://github.com/0xc000022070/zen-browser-flake/issues/84.
2025-08-15 10:10:14 -05:00
Florian
4d72db5b12 feat: add aarch64-darwin (macOS) support (#80) 2025-07-25 23:04:26 -05:00
Luis Quiñones
c18083f6dc ci(github/update): only use retry logic for JSON api calls
The uploaded artifacts were corrupted thanks to the new implementation.
2025-06-08 11:56:37 -05:00
Luis Quiñones
a1ed62298f ci(github/update): use wrapper function to retry requests to curl and gh 2025-06-08 02:23:17 -05:00
Luis Quiñones
98d5e7ae2b ci(github/update): error trace logs are sent to stderr 2025-06-08 01:56:14 -05:00
Luis Quiñones
d612a652a4 revert: "ci(update): add logic to retry some requests to GitHub API"
This reverts commit 439ac110a9.
2025-06-08 01:54:22 -05:00
Luis Quiñones
439ac110a9 ci(update): add logic to retry some requests to GitHub API
Look this shit:
https://github.com/0xc000022070/zen-browser-flake/actions/runs/15260014148/job/42915959078
2025-06-07 22:08:30 -05:00
Luis Quiñones
50065c8bee ci(update): specific format for twilight release title (#60)
Watch your back
2025-05-12 12:39:13 -05:00
Luis Quiñones
be0384aad3 revert: "ci(update): better twilight release name (#57)" (#58)
This reverts commit 1965b827dc.
2025-05-08 15:06:54 -05:00
Luis Quiñones
1965b827dc ci(update): better twilight release name (#57) 2025-05-08 12:37:57 -05:00
Luis Quiñones
9489495f70 ci(update): prefer semver in twilight release name + update release notes 2025-04-26 09:08:47 -05:00
Luis Quiñones
e47f96fa8e ci(update): fix format of generated commit 2025-04-16 09:08:39 -05:00
Luis Quiñones
847dce4051 ci(update): generated commit will have conventional commits format 2025-04-15 14:39:41 -05:00
Luis Quiñones
b6b61a5d36 ci(update/twilight): using updated at epoch for commit, release name and notes 2025-03-15 01:35:25 -05:00
Luis Quiñones
cd9be7eff9 ci(update): removing invalid control characters from gh response 2025-03-15 01:23:45 -05:00
Luis Quiñones
9a6a8b54fd ci(update): using artifact timestamp to detect if there is any update in twilight release artifacts
This commit might resolve: https://github.com/0xc000022070/zen-browser-flake/issues/26

I should say thanks to Silenc3IsGold3n because the idea of using the updated_at field
belongs to him/her.
2025-03-15 01:04:20 -05:00
Luis Quiñones
d5de27c48b ci(update): twilight version won't be updated until a workaround is applied 2025-03-15 00:20:23 -05:00
Luis Quiñones
e3654e1d95 ci(update): using correct version var to create twilight release name 2025-03-09 16:14:21 -05:00
Luis Quiñones
6dceddfe8e ci(update): support for twilight releases based on the same tag with same commit
I hate that
2025-03-08 11:13:11 -05:00
Luis Quiñones
d00e735e0b fix(github/update): using correct entry name for beta releases 2025-02-24 04:54:20 -05:00
Luis Quiñones
dd6ba8e792 feat: variant version will be the default version + official variant
The official variant will pin the official binaries from
github:zen-browser/desktop, that's the option for people that doesn't
trust the binaries of this repository.

In other hand, the "twilight" package is pinned with artifacts that we
store in this repository. The reason why this is default now is because
I decided to follow the philosophy that is available in the official
NixOS page(https://nixos.org/): reproducible, declarative and reliable.
I know this could be a little bit invasive for some people but I think
that they're just a minority and this is a problem that should be solved
now given the time that has been passed since twilight was implemented.
2025-02-15 19:40:23 -05:00
Luis Quiñones
23dd63e6ae fix(github/update): aarch64 artifacts for resilient are referenced in source file
the problem with the previous version of the script is that the HTTP
query to get the release artifacts to download and upload in our
repository wasn't retrieving by the specified architecture, leading us
to have an output with two lines with the following order:
 1. [...x84_64]
 2. [...aarch64]

At least now it supports already uploaded artifacts so while developing
for example, you won't need to remove the artifact from the repository
to keep trying.

Secondary changes:
 - We have better logs to trace the flow that every binary had in the update script
2025-02-15 19:21:58 -05:00
Luis Quiñones
12edc373eb feat: resilient variant of twilight version 2025-02-10 22:19:49 -05:00
Oliver Geneser
ba822e10f3 fix: change from tar.bz2 to tar.xz 2025-02-01 15:10:44 +01:00
Luis Quiñones
4476798b07 ci(update): using short SHA1 for commit message of twilight releases 2025-01-18 22:07:35 -05:00
clementpoiret
b02792c3b9 fix: new naming scheme 2025-01-10 14:42:33 +01:00
Luis Quiñones
d7c2e4db11 ci(update): updated regexp to extract twilight version from github release title 2025-01-03 15:23:50 -05:00
Luis Quiñones
5a6f4b324f chore: removed name entry from sources.json file 2024-12-31 16:56:22 -05:00
Luis Quiñones
9730693e92 ci(update): updated log when local source appears outdated 2024-12-31 16:53:08 -05:00
Luis Quiñones
1e252e0e5f ci(update): extracting twilight semver from release name 2024-12-31 16:47:50 -05:00
Luis Quiñones
6af8216a80 ci(update): using nix store prefetch with --unpack option 2024-12-31 16:07:26 -05:00
Luis Quiñones
3d26db3a16 ci: script to update everything can produce good commit messages 2024-12-31 15:44:22 -05:00
Luis Quiñones
07a074f2f7 ci: partial integration with new script to fetch new versions 2024-12-31 15:09:28 -05:00