Releases: APESCIC/MyAPES-Account
Release list
0.31.12 Beta
Local-first ship-gate workflow
Agent shipping workflow now verifies changes on local dev before a PR and treats Cloudron deploy as the last post-merge step.
Changes
- Add a pre-merge local dev verify gate to ship-gate rules and skills.
- Reorder post-merge gates to changelog metadata, Cloudron deploy last, then live hub and GitHub Release verification.
- Add composer pre-pr-verify to wrap pre-merge checks and a non-destructive local bootstrap.
Affected areas
- Agent workflow documentation
- Local development scripts
References
MyAPES Core 0.31.12 (2026-08-30) · stable · patch
0.31.11 Beta
Move GitHub support links to sidebar
Public GitHub support links now live in a sidebar App Support section with icon-led pills instead of the shared footer.
Changes
- Move GitHub, Open an issue, and Discussions links from the shared footer into a new App Support section at the bottom of the left sidebar.
- Show App Support below Log out for signed-in users and after the theme toggle for guests.
- Style each support link as a pill with a Lucide icon and a hover lift effect.
- Keep the Change Log Hub Feedback and source block unchanged.
Affected areas
- Shared layout sidebar
- Shared layout footer
- Public navigation chrome
References
MyAPES Core 0.31.11 (2026-08-29) · stable · patch
0.31.10 Beta
Version-stamped deploy and Beta release titles
Cloudron deploy now stamps GitHub Deployments, publishes GitHub Releases automatically, and uses the display title format {VERSION} Beta for deployments and releases.
Changes
- Automate Cloudron deploy GitHub Release publishing on successful deploy with notes from scripts/deploy/github-release-notes.sh.
- Set deployment description and GitHub Release display name to {VERSION} Beta; keep tags as v{VERSION}.
- Change workflow run-name to {VERSION} Beta without a Deploy prefix.
- Add scripts/github/rename-release-titles.sh and scripts/github/migrate-beta-milestones.sh for release title and milestone migration.
Affected areas
- Cloudron deployment workflow
- GitHub Releases and Deployments
- Agent ship-gate and issue milestone guidance
References
MyAPES Core 0.31.10 (2026-08-29) · stable · patch
GitHub Release backfill and changelog sync
All 72 documented app versions now have matching GitHub Release tags (v{VERSION}), and release prepare requires a pull request reference so future versions stay aligned with GitHub.
Changes
- Backfill GitHub Releases and tags for v0.1.0 through v0.31.6 mapped to their merge commits on main.
- Add scripts/local/map-release-commits.mjs and scripts/local/backfill-github-releases.mjs with dry-run, resume, and batch support.
- Require --pr on myapes:changelog-prepare so every new release cites its merging pull request.
- Show a GitHub Release link in the Change Log Hub Source section for staff and admin viewers.
- Document GitHub Release tag parity and the deploy SHA versus version introduction commit distinction in README and ship-gate guidance.
Affected areas
- GitHub Releases and tags
- Release metadata workflow
- Change Log Hub staff references
- Agent ship-gate documentation
Version rationale
Patch release: aligns external GitHub versioning with in-app semver and tightens release metadata hygiene without changing production application behaviour.
References
MyAPES Core 0.31.9 (2026-08-29) · stable · patch
Laravel Boost MCP for local dev
Summary
Local developers can use Laravel Boost MCP in Cursor with Laragon, including AI guidelines and skills wired for this repository.
Changes
- Install laravel/boost and add boost.json for Cursor MCP integration.
- Add Cursor AI guidelines and Laravel, Tailwind, and testing skills under .cursor/skills.
- Document Laragon PHP 8.4 requirement for boost:mcp in AGENTS.md.
Affected areas
- Local development documentation
- Composer dev dependencies
- Cursor agent configuration
Notes
Patch release: local development tooling and documentation only; no production application behaviour change.
Known limitation: boost:mcp requires PHP 8.4 or newer; Laragon Apache may need a PHP 8.4 FastCGI handler until Laragon ships 8.4 mod_php.
Laragon local dev testing setup
Windows developers can run MyAPES Core on a Laragon Apache virtual host with a dedicated env profile, bootstrap switch, and dev launcher that skips artisan serve.
Changes
- Add .env.laragon.example with vhost URLs and VITE_DEV_SERVER_URL for Laragon Apache workflows.
- Extend bootstrap.ps1 with -Laragon and optional -AppUrl for SQLite QA setup on a .test hostname.
- Add composer run dev:laragon and dev-laragon.ps1 so Vite, queue, and logs run without php artisan serve.
- Tune Vite dev-server HMR settings for pages served from a Laragon virtual host.
- Document Laragon prerequisites, vhost setup, daily dev loop, and troubleshooting in README and AGENTS.md.
Affected areas
- Local development documentation
- Local bootstrap and dev launcher scripts
References
MyAPES Core 0.31.6 (2026-08-29) · stable · patch
Mark v1.0.0 Beta complete in agent order
Agent implement order now records v1.0.0 Beta as complete on live and no longer blocks starting v1.1.0 Public UX work.
Changes
- Mark milestone 1 / v1.0.0 Beta complete on live v0.31.2 in AGENTS.md, including closed epic #91 and live-verify #159.
- Remove the remaining-gate wording that blocked v1.1.0 until #159 closed on live.
- Leave the documented v1.1.0 and v1.2.0 implement lists ready for the next asked slice.
Affected areas
- Agent implement-order documentation
- Release and ship workflow guidance
References
MyAPES Core 0.31.5 (2026-08-29) · stable · patch
Ship-gate pre-PR commit options
Ship-gate now asks before the first commit or push: when committing is best, plus numbered options to commit, open a PR, save WIP, or keep working uncommitted.
Changes
- Add a Before PR / commit gate to the ship-gate agent rule and skill, including when-to-commit guidance.
- Offer Next-actions options for commit and PR, commit only, WIP checkpoint, keep uncommitted, or stop.
- Document the commit gate in the AGENTS.md end-of-work checklist before open/update PR.
Affected areas
- Agent ship-gate documentation
- Release and ship workflow guidance
References
MyAPES Core 0.31.4 (2026-08-29) · stable · patch
Manual Cloudron deploy and ship-gate workflow
Cloudron deploy is operator-triggered only. Cursor agents follow a ship-gate: ask after CI, ask to deploy after merge, verify Change Log hubs, then ask whether to create a GitHub Release.
Changes
- Stop auto-deploy on green main; Deploy MyAPES Core to Cloudron runs only on workflow_dispatch.
- Add ship-gate agent rule and skill with next-actions menus for merge, deploy, changelog hubs, and GitHub Release.
- Document that the app Change Log Hub updates from releases.json on the same Cloudron deploy, and that sibling website changelogs need an explicit operator ask.
Affected areas
- Cloudron deployment workflow
- Agent ship-gate documentation
- Public Change Log Hub (via deploy)
Version rationale
Patch release: changes how operators and agents trigger deploy and release without changing application product features for end users.
References
MyAPES Core 0.31.3 (2026-08-29) · stable · patch
Redirect stale Super Admin plugins and groups URLs
abe791e 
cursoragent
Cursor Agent
Stale Super Admin addresses for Plugins and Groups now send people to the live Admin pages instead of a bare Laravel 404.
Changes
- Redirect /superadmin/plugins and the older /superadmin/modules address to the live Plugins page at /admin/modules.
- Redirect /superadmin/groups to the live Groups address at /admin/groups, which continues into the Access Groups tab.
- Keep Super Admin navigation pointed at the live Access and Plugins pages so those chrome links do not use the stale addresses.
Affected areas
- Super Admin navigation
- Super Admin compatibility URLs
Version rationale
Patch release: restores existing Super Admin Plugins and Groups destinations without adding a new workspace.
References
MyAPES Core 0.31.2 (2026-08-28) · stable · patch