Release 1.0.2 with localized sky overlay and cloud-resistant display fit
All checks were successful
Release AstroFrame / packages (push) Successful in 1m1s

This commit is contained in:
Elijah 2026-10-03 20:36:20 -07:00
parent 1e8e8c88fe
commit 6b56c0b122
16 changed files with 227 additions and 24 deletions

View file

@ -40,6 +40,8 @@ To uninstall a script-installed Linux copy, close AstroFrame and remove only `~/
## Settings and updates
Version **1.0.2** corrects the spatial preview overlay. Pink shows the strongest positive sky structure against the clean session reference; the display fit resists bright cloud contamination, and weak background residuals are suppressed. Both bright and moderately bright cloud patches remain visible. The grid shows regional stellar flux. This is supporting evidence rather than an exact cloud boundary. Existing saved projects reconstruct the display from cached catalogs without changing classification metrics or human decisions. See [1.0.2 release notes](release-notes/1.0.2.md).
Open **Settings → Updates** for the installed version, update status, last successful check, automatic-check preference, and **Check for updates**. The sidebar and independent settings store leave room for future categories.
Installed packages check on launch and every six hours while running. A persistent **Settings · Update available** indicator appears when a newer stable version is found. **Install update and restart** downloads the update, validates its package checksum, saves the project and restarts. Analysis, export and saving block installation; if work starts during download, the package remains ready for a later restart. Projects and settings survive updates. Failed checks display an error rather than claiming the app is up to date. Source-tree builds explain that installing a package enables updates.
@ -59,12 +61,12 @@ Once this workflow is committed and pushed, enable Actions for the AstroFrame re
To release a new version:
```powershell
./packaging/Set-Version.ps1 -Version 1.0.2
./packaging/Set-Version.ps1 -Version 1.0.3
git add Directory.Build.props
git commit -m "Release 1.0.2"
git commit -m "Release 1.0.3"
git push origin main
git tag v1.0.2
git push origin v1.0.2
git tag v1.0.3
git push origin v1.0.3
```
Include all intended source changes in the release commit before tagging. The pushed tag is the publication trigger; ordinary commits to `main` run the build and checks without publishing. The version in `Directory.Build.props` must exactly match the tag. Version `v1.0.1` is published; `v1.0.0` remains an unpublished tag from the first failed publishing attempt. Choose a new version for each later release.
@ -89,7 +91,7 @@ The Windows script cross-packages both platforms. Results appear in `artifacts/r
On Linux with a .NET 10 SDK:
```sh
bash packaging/release.sh 1.0.1
bash packaging/release.sh 1.0.2
```
That script builds the Linux channel. The tool manifest pins Velopack CLI 1.2.161, matching the application's SDK dependency. Building on Windows is enough to create both packages, but compatibility should still be checked on target Linux desktops.