23 Commits

Include renames

Author	SHA1	Message	Date
gitea-actions	458b2b272d	chore(release): v1.0.21 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.21.	2026-08-15 19:41:02 +00:00
gitea-actions	d854dff091	chore(release): v1.0.20 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.20.	2026-08-15 18:59:38 +00:00
gitea-actions	ca6432efc8	chore(release): v1.0.19 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.19.	2026-08-15 08:33:01 +00:00
rmancinas	7be897ef2b	chore(release): v1.0.18	2026-08-11 13:17:45 -07:00
rmancinas	3b02c6944f	chore(release): v1.0.17	2026-08-11 12:56:52 -07:00
gitea-actions	5352d49ecf	chore(release): v1.0.16 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.16.	2026-08-07 05:06:42 +00:00
gitea-actions	7981c715ce	chore(release): v1.0.15 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.15.	2026-08-05 07:37:01 +00:00
gitea-actions	458e67340c	chore(release): v1.0.14 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.14.	2026-08-05 05:33:49 +00:00
gitea-actions	2620559975	chore(release): v1.0.13 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.13.	2026-08-05 05:23:57 +00:00
gitea-actions	d38bbc52ec	chore(release): v1.0.12 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.12.	2026-08-05 04:40:07 +00:00
gitea-actions	4a929f7e7c	chore(release): v1.0.11 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.11.	2026-08-04 00:55:49 +00:00
gitea-actions	f269dc8bfa	chore(release): v1.0.10 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.10.	2026-08-04 00:43:02 +00:00
gitea-actions	7f1bfe906e	chore(release): v1.0.9 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.9.	2026-08-04 00:31:58 +00:00
gitea-actions	127eaa9689	chore(release): v1.0.8 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.8.	2026-08-03 20:47:55 +00:00
gitea-actions	2fa12890f5	chore(release): v1.0.7 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.7.	2026-08-02 20:29:10 +00:00
gitea-actions	905fa31e47	chore(release): v1.0.6 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.6.	2026-08-02 02:06:12 +00:00
gitea-actions	98f7aa8a2d	chore(release): v1.0.5 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.5.	2026-08-01 09:22:56 +00:00
gitea-actions	70fe425043	chore(release): v1.0.4 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.4.	2026-08-01 09:09:15 +00:00
gitea-actions	e082113640	chore(release): v1.0.3 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.3.	2026-08-01 08:45:42 +00:00
gitea-actions	a9b4aab7ec	chore(release): v1.0.2 ... Cut by rmancinas via the "Cut release" workflow. Pushing the tag triggers build.yml; deploy separately with tag=1.0.2.	2026-08-01 08:23:07 +00:00
rmancinasandClaude Opus 5	121952fdc1	chore(release): v1.0.1 ... v1.0.0's images were built from db2bd54, which predates the full-hash footer. Deploying 1.0.0 would ship the abbreviated footer, so the version that actually goes to galactus is 1.0.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 16:38:06 -07:00
rmancinasandClaude Opus 5	db2bd545a1	chore(release): v1.0.0 ... Every manifest still read 0.1.0 while the deployed images were addressed by the moving tag `latest`. That combination is what hid the stale-image bug: a checkout could not be placed against a running container, and `latest` silently kept serving two-commit-old web code through a green deploy. Tagging v1.0.0 makes docker/metadata-action publish immutable `1.0.0` and `1.0` image tags, so deploys can name a version instead of a moving target. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 16:21:35 -07:00
rmancinas	27118f0df2	Initial scaffold: unified customer/insurance/utilities platform ... Next.js + NestJS + Prisma (MySQL) monorepo replacing the legacy PHP internal app. Includes a session-based auth module with Argon2 password hashing and global input validation (replacing the old app's SQL injection and plaintext password comparison), the full target Prisma schema for customers/insurance/utilities/shared ledger/bank register, Docker Compose + Dockerfiles, and an Access-to-staging migration pipeline (migration/) already run against the real source databases. See PLAN.md and RESUME.md for the full architecture and session history.	2026-07-22 01:29:56 -07:00