Skip to content

chore(release): v2026.10.11 - #6

Merged
Awesome-Ace22 merged 4 commits into
mainfrom
release/v2026.10.11
Oct 19, 2026
Merged

Awesome-Ace22 merged 4 commits into
mainfrom
release/v2026.10.11

Conversation

@Nova-Server-UTAT

Copy link
Copy Markdown
Contributor

Brings v2026.10.11 into main: exactly the commit that was tested (cold flow test).

Release notes: https://github.com/UTATRocketry/Nova-Collected/releases/tag/v2026.10.11

Merge with "Create a merge commit", not squash, so the tested commit is kept (CONTRIBUTING.md section 5).

Awesome-Ace22 and others added 4 commits August 18, 2026 18:27
…iguration

- Implemented a new component `RadioConfigView` that provides a read-only view of the FMC-authoritative radio configuration record.
- Added utility functions for formatting values such as frequency and time.
- Integrated transaction badges to indicate the status of the radio configuration.
- Updated the API to support sending and receiving radio configuration data.
- Enhanced flight data parsing to include radio configuration state and details.
- Updated the tools index and manifest to include the new radio tool.
aux_flags bits 1 and 2 are permanently reserved and never emitted, so the
present/recording rows always rendered a hard-coded "no" next to real telemetry.
Show the rail as the EPB echoed it and the FMC's own countdown.

A blank auto-stop now omits the field, so the FMC applies its persisted default
rather than being told "never stop"; 0 still means no timer.
ops/Nova.ps1 regenerates .env.production from ops/nova.config.ps1 for
whichever environment is being launched, and next build emits
next-env.d.ts; both are output, not source, and kept every checkout
permanently dirty.
@Awesome-Ace22
Awesome-Ace22 merged commit 2008529 into main Oct 19, 2026
1 of 2 checks passed
@Awesome-Ace22
Awesome-Ace22 deleted the release/v2026.10.11 branch October 19, 2026 20:37
Awesome-Ace22 added a commit that referenced this pull request Oct 20, 2026
…ncy (#10)

## What and why
Removes `@next/swc-win32-x64-msvc` from `dependencies`. It is Next.js's
Windows-only compiler binary, and as a direct dependency npm can't skip
it on other platforms. `npm ci` on the Linux CI runner failed with
`EBADPLATFORM`, so the `build` check failed on the v2026.10.11 release
PR (#6) before typecheck or build ran. It was pinned at `^16.3.0` while
`next` is 15.5.x.

Windows doesn't need it listed. Next declares it as an optional
dependency, so npm still installs the matching 15.5.19 binary there. The
lockfile now has it as an `optional` 15.5.19 entry instead of the 16.3.0
one.

Closes UTATRocketry/Nova-Collected#27

## How was this tested?
- [ ] 1 Unit / Automated Test - CI
- [ ] 2 Simulator Test - testing procedure with the hardware simulators
- [ ] 3 Bench Test - testing procedure on the dev stack, with some real
hardware
- [ ] 4 Integration Test - full engine test procedure, real hardware, no
propellants

<!-- What you did and what you saw: -->
- [x] None - UI, docs or tooling only
- [ ] Changes how a sensor is read, converted or shown
- [ ] Changes how an actuator is commanded, or safety rules, interlocks,
timeouts or sequencing → add the `hardware-risk` label; a lead must
approve
- [ ] Changes a message format, MQTT topic or FAS protocol that another
repo depends on → title needs `!`, link the matching PRs:


## Checklist
- [x] Targets `dev` (or `main` for a release/hotfix, or with a reason
given above)
- [x] Branch is up to date ("Update branch" button)
- [x] No station config/calibrations, data files, secrets, `.env` files
or build output committed
- [x] README/docs updated if behaviour changed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants