Compare commits

..

No commits in common. "7cbd4944bdabd17ab8f1a85fe81805a5eaa3ce67" and "da3d080124a344716571f1eef3c6ce804b583599" have entirely different histories.

4 changed files with 22 additions and 32 deletions

View file

@ -104,12 +104,10 @@ jobs:
chmod +x ./gradlew chmod +x ./gradlew
./gradlew assembleRelease -PandroidVersionName="$ANDROID_VERSION_NAME" -PandroidVersionCode="$ANDROID_VERSION_CODE" ./gradlew assembleRelease -PandroidVersionName="$ANDROID_VERSION_NAME" -PandroidVersionCode="$ANDROID_VERSION_CODE"
# Nom de fichier stable, jamais versionné : la page d'accueil (#65) # Nom de fichier stable, jamais versionné : c'est ce qui permet à la
# pointe vers /releases/latest (Forgejo n'a pas l'équivalent du # page d'accueil (#65) de pointer en permanence vers
# raccourci GitHub /releases/latest/download/<fichier>, seul # /releases/latest/download/batchcooking.apk sans jamais changer de
# /releases/latest lui-même résout) — un nom stable évite au moins que # lien d'une release à l'autre.
# l'utilisateur voie un nom de fichier différent à chaque release une
# fois sur la page.
- name: Renomme l'APK sous un nom stable - name: Renomme l'APK sous un nom stable
run: cp apps/web/android/app/build/outputs/apk/release/app-release.apk batchcooking.apk run: cp apps/web/android/app/build/outputs/apk/release/app-release.apk batchcooking.apk

View file

@ -16,14 +16,14 @@ Then("I should see the landing call to action", () => {
}); });
// The Android build is distributed as a Forgejo release asset with a stable // The Android build is distributed as a Forgejo release asset with a stable
// filename (issue #64 builds/attaches it). Points at the release page // filename (issue #64 builds/attaches it). We only assert the link is there
// itself, not a direct file URL: Forgejo has no GitHub-style // and points at the right URL — the file itself is external to the suite.
// `/releases/latest/download/<file>` shortcut, only `/releases/latest`
// resolves (verified live against the first real release). We only assert
// the link is there and points at the right URL — the file itself is
// external to the suite.
Then("I should see the Android download link", () => { Then("I should see the Android download link", () => {
cy.get(".landing__hero .landing__mobile-link") cy.get(".landing__hero .landing__mobile-link")
.should("be.visible") .should("be.visible")
.and("have.attr", "href", "https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest"); .and(
"have.attr",
"href",
"https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest/download/batchcooking.apk",
);
}); });

View file

@ -10,14 +10,11 @@ import { useAppUpdateCheck } from "./useAppUpdateCheck";
* `<dialog>`: a version check is informative, never something that should * `<dialog>`: a version check is informative, never something that should
* block the rest of the page. * block the rest of the page.
* *
* "Mettre à jour" opens the Forgejo release page externally (not a direct * "Mettre à jour" opens the download link externally (the system browser
* file link — Forgejo has no GitHub-style `/releases/latest/download/<file>` * handles the download + Android's own install prompt) rather than an
* shortcut, only `/releases/latest` itself resolves; verified live against * in-app `PackageInstaller` flow — no `REQUEST_INSTALL_PACKAGES` permission,
* the first real release) rather than an in-app `PackageInstaller` flow — * no extra native code, for a marginal UX gain (see issue #66's own
* no `REQUEST_INSTALL_PACKAGES` permission, no extra native code, for a * hors-scope).
* marginal UX gain (see issue #66's own hors-scope). One extra tap on the
* release page to reach the actual asset, then the system browser handles
* the download + Android's own install prompt as before.
*/ */
export function UpdateBanner() { export function UpdateBanner() {
const { t } = useTranslation(); const { t } = useTranslation();
@ -33,7 +30,7 @@ export function UpdateBanner() {
<div className="update-banner__actions"> <div className="update-banner__actions">
<a <a
className="update-banner__update" className="update-banner__update"
href="https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest" href="https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest/download/batchcooking.apk"
target="_blank" target="_blank"
rel="noreferrer" rel="noreferrer"
> >

View file

@ -53,19 +53,14 @@ export function LandingPage() {
{/* {/*
* Secondary action — an account is needed on any platform, so the * Secondary action — an account is needed on any platform, so the
* Android build is a discreet link under the CTA row, not a third * Android build is a discreet link under the CTA row, not a third
* button. Points at the Forgejo "latest release" page (NOT a * button. Points at the Forgejo "latest release" asset with a
* direct-download URL): Forgejo, unlike GitHub, has no * stable filename (see issue #64); 404s until that pipeline ships,
* `/releases/latest/download/<file>` compound route — only * accepted as a transient state. The hint is honest that this is a
* `/releases/latest` itself resolves (redirects to the release's * sideloaded .apk, not a Play Store listing.
* own page), verified live against the first real v0.2.0 release.
* One extra click via Forgejo's own release page to reach the
* actual `batchcooking.apk` asset, but a link that will always
* resolve rather than a shortcut that 404s. The hint is honest
* that this is a sideloaded .apk, not a Play Store listing.
*/} */}
<a <a
className="landing__mobile-link" className="landing__mobile-link"
href="https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest" href="https://git.dev.kyuno.fr/kyuno/batchCooking/releases/latest/download/batchcooking.apk"
> >
<Smartphone aria-hidden /> <Smartphone aria-hidden />
{t("landing.hero.mobileDownload")} {t("landing.hero.mobileDownload")}