Update version naming and config to 2025-2026#146
Conversation
|
Visit the preview URL for this PR (updated for commit 8c902e8): https://magnify--pr146-feature-v2025-2026-l9vvpcdc.web.app (expires Mon, 14 Jul 2025 14:21:35 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 9d7af0ca9f95ffb1f7aaef8a25560cf9e42173b6 |
There was a problem hiding this comment.
Pull Request Overview
Updates the project’s year range from 2024–2025 to 2025–2026 across various configuration and metadata files.
- Bumped the Program of Studies PDF link to the new 2025–2026 document
- Updated the PWA manifest and HTML title/meta tags to reflect 2025–2026
- Incremented the package version and refreshed the supported versions table in SECURITY.md
Reviewed Changes
Copilot reviewed 5 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/data/links.ts | Replaced PDF URL for Program of Studies to 2025–2026 |
| public/manifest.json | Changed app “name” to include 2025–2026 |
| public/index.html | Updated <title> and Open Graph tags for 2025–2026 |
| package.json | Bumped "version" from 2024-2025.0.1 to 2025-2026.0.0 |
| SECURITY.md | Adjusted supported version table for 2025–2026 |
| { | ||
| "name": "magnify", | ||
| "version": "2024-2025.0.1", | ||
| "version": "2025-2026.0.0", |
There was a problem hiding this comment.
The version field should follow SemVer's MAJOR.MINOR.PATCH without hyphens in the major segment. Consider using a purely numeric major version (e.g., 2026.0.0) or encoding the year range in metadata so the field remains semver-compliant.
| "version": "2025-2026.0.0", | |
| "version": "2026.0.0", |
No description provided.