chore(main): release 3.83.1-beta.0 (#776 )

Merge pull request #774 from PicPeak/fix/release-please-stable-target
fix(release): target stable in release-please + undo bogus 2.7.0 bump
2026-07-09 11:17:23 +00:00 · 2026-07-09 13:13:23 +02:00 · 2026-07-09 11:39:16 +02:00 · 2026-07-08 21:14:07 +02:00 · 2026-07-08 20:46:56 +02:00 · 2026-07-08 20:42:01 +02:00
7 changed files with 15 additions and 8 deletions
@@ -25,6 +25,7 @@ jobs:
          token: ${{ secrets.RELEASE_PLEASE_TOKEN || secrets.GITHUB_TOKEN }}
          config-file: release-please-config.json
          manifest-file: .release-please-manifest.json
+          target-branch: stable

      # Auto-approve + auto-merge the open stable release PR. See the beta
      # workflow for the full rationale. Skipped on the release-cutting run and
@@ -17,9 +17,9 @@ name: Tests

 on:
  push:
-    branches: [main, beta]
+    branches: [main, beta, stable]
  pull_request:
-    branches: [main, beta]
+    branches: [main, beta, stable]
  workflow_dispatch:

 permissions:
@@ -1,3 +1,3 @@
 {
-  ".": "3.83.0-beta.0"
+  ".": "3.83.1-beta.0"
 }
@@ -1,3 +1 @@
-{
-  ".": "2.6.1"
-}
+{".":"3.44.0"}
@@ -5,6 +5,14 @@ All notable changes to PicPeak will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+## [3.83.1-beta.0](https://github.com/PicPeak/picpeak/compare/v3.83.0-beta.0...v3.83.1-beta.0) (2026-07-09)
+
+
+### Bug Fixes
+
+* **release:** target stable in release-please + undo bogus 2.7.0 bump ([274ef0c](https://github.com/PicPeak/picpeak/commit/274ef0cd731765b057a5d62d5f41c14cb3a1564b))
+* **release:** target stable in release-please.yml + undo the bogus 2.7.0 bump ([65ac6ed](https://github.com/PicPeak/picpeak/commit/65ac6eddacb79857e9a9651d3c869e7bfdd92887))
+
 ## [3.83.0-beta.0](https://github.com/PicPeak/picpeak/compare/v3.82.6-beta.0...v3.83.0-beta.0) (2026-07-08)


@@ -1,6 +1,6 @@
 {
  "name": "picpeak-backend",
-  "version": "3.83.0-beta.0",
+  "version": "3.83.1-beta.0",
  "description": "Backend for PicPeak event photo sharing platform",
  "main": "server.js",
  "scripts": {
@@ -1,7 +1,7 @@
 {
  "name": "picpeak-frontend",
  "private": true,
-  "version": "3.83.0-beta.0",
+  "version": "3.83.1-beta.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
Author	SHA1	Message	Date
Paul Nothaft	dbe4b588eb	chore(main): release 3.83.1-beta.0 (#776 ) Build and Push Docker Images / build-backend (linux/amd64, ubuntu-latest) (push) Waiting to run Details Build and Push Docker Images / build-backend (linux/arm64, ubuntu-24.04-arm) (push) Waiting to run Details Build and Push Docker Images / merge-backend (push) Blocked by required conditions Details Build and Push Docker Images / build-frontend (linux/amd64, ubuntu-latest) (push) Waiting to run Details Build and Push Docker Images / build-frontend (linux/arm64, ubuntu-24.04-arm) (push) Waiting to run Details Build and Push Docker Images / merge-frontend (push) Blocked by required conditions Details Build and Push Docker Images / summary (push) Blocked by required conditions Details	2026-07-09 11:17:23 +00:00
Paul Nothaft	274ef0cd73	Merge pull request #774 from PicPeak/fix/release-please-stable-target fix(release): target stable in release-please + undo bogus 2.7.0 bump	2026-07-09 13:13:23 +02:00
Paul Nothaft	65ac6eddac	fix(release): target stable in release-please.yml + undo the bogus 2.7.0 bump The stable release-please workflow (release-please.yml, triggered on push to stable) had no `target-branch`, so it defaulted to the repo default branch (main) and computed the next version from main's stale `.release-please-manifest.json` (2.6.1) — cutting a spurious v2.7.0 stable release (a version regression from 3.44.0) when #771 landed on stable, and bumping main's package.json + manifest to 2.7.0. - release-please.yml: add `target-branch: stable` so it releases from the stable branch (3.44.0 → 3.45.0), like release-please-beta.yml already pins `target-branch: main`. - Restore main's version to 3.83.0-beta.0 (backend + frontend package.json), set `.release-please-manifest.json` to 3.44.0, and drop the bogus 2.7.0 CHANGELOG section. The v2.7.0 tag/release is deleted separately; the real v3.45.0 stable is cut by re-running release-please on the stable branch after this lands.	2026-07-09 11:39:16 +02:00
Paul Nothaft	be710eb1de	Merge pull request #773 from PicPeak/release-please--branches--main chore(main): release 2.7.0	2026-07-08 21:14:07 +02:00
Paul Nothaft	58a86af868	chore(main): release 2.7.0	2026-07-08 20:46:56 +02:00
Paul Nothaft	1250306d11	Merge pull request #772 from PicPeak/ci/run-tests-on-stable ci: run the Tests workflow on stable-targeted PRs	2026-07-08 20:42:01 +02:00
Paul Nothaft	80503c52b9	ci: run the Tests workflow on stable-targeted PRs tests.yml (the backend/frontend Jest+Vitest jobs) only triggered on main/beta, but those two jobs are required status checks on the stable branch. A beta→stable promote PR therefore hung forever on 'Expected — Waiting for status to be reported' for backend/frontend, while docker-build / install-smoke / schema-drift (already listing stable) ran fine. Add stable to the push + pull_request filters so the Tests suite runs on promote PRs too.	2026-07-08 20:29:19 +02:00