RunCove v0.4.1

RunCove v0.4.1

RunCove v0.4.1 is a fix release for v0.4.0. It changes no features and needs no
database migration: if you are already on v0.4.0, this is a drop-in replacement.

Fixed

• Two ordered starts that share a profile no longer fail each other. Starting
  two launch groups that both contain the same database, or starting a group while
  a restore is bringing the same profiles back, used to fail whichever arrived
  second with an "already starting" message the user had done nothing to cause.
  Each one now waits for the shared profile to settle and carries on, so the
  startup order every group promises still holds and a profile the other one
  already brought up simply counts as started.
• SHA256SUMS.txt now passes sha256sum -c. The v0.4.0 file put three spaces
  between each hash and its filename where the format allows exactly two, so every
  line failed to open on a byte-perfect download. The workflow now writes the
  accepted format and verifies the file before publishing, in the same job that
  writes it.
• A failed restore names the profile it stopped at as Project / Profile
  rather than printing an internal id, which is what a whole-group failure has
  always done.
• A restore and a whole-group start are no longer offered at the same time.
  Waiting makes overlapping them correct, but the second would only sit and wait
  for work already underway, so the button that starts it is disabled while the
  first runs.
• The desktop executable is built with the release settings it was always meant
  to get. They were written once at the repository root, and the desktop app is a
  separate Cargo package rather than a workspace member, so it was the only shipped
  binary built without link-time optimization. Measured on the same builder and
  compiler as v0.4.0, the executable goes from 13,212,672 to 11,978,752 bytes — 9%
  smaller, and about 91 KB off the download once compressed. Nothing about how
  RunCove behaves changes.

Upgrade Note

No migration runs and no backup is needed if you are coming from v0.4.0. This
release reads the same schema version 3 database.

Coming from v0.3.0 or earlier, the migration described in v0.4.0's notes still
applies: the database upgrades to schema version 3 on first launch, each step runs
in one transaction and stays at the previous version if it fails, and a successful
upgrade has no downgrade path — v0.3.0 and earlier cannot open a version 3
database. Copy runcove.sqlite3 out of %LOCALAPPDATA%\com.abysswhale.runcove\
first if you may need to go back.

Known Limitations

• A launch group starts and stops only when you press its button. There is no
  start-at-login and no automatic project startup, by design.
• In the rare case that a run log archive's final buffered flush fails, the
  archive line count can over-report which buffered line reached disk. The byte
  count is measured from the file, and normal writes are unaffected.
• The SHA256SUMS.txt published with v0.4.0 still has the formatting defect
  above; it cannot be changed after the fact. Verify that older release with
  sed -E 's/^([0-9a-f]{64})[[:space:]]+/\1 /' SHA256SUMS.txt | sha256sum -c -.
  This release's file needs no workaround.

Downloads

• runcove-desktop-windows-x86_64-portable.zip contains the unsigned Windows
  desktop application.
• runcove-cli-* archives contain the cross-platform runcove CLI and a
  compatibility executable for existing scripts.
• SHA256SUMS.txt contains SHA-256 checksums for every binary archive.

Windows SmartScreen may show an unknown-publisher warning because the desktop
executable is not code-signed. Download it only from this GitHub release and
verify the archive against SHA256SUMS.txt. Microsoft Edge WebView2 Runtime is
required and is included with current Windows 11 systems.

To verify, put SHA256SUMS.txt beside the archives you downloaded and run:

sha256sum -c SHA256SUMS.txt

# Windows PowerShell, no sha256sum available
(Get-FileHash runcove-desktop-windows-x86_64-portable.zip -Algorithm SHA256).Hash
# compare, case-insensitively, against the matching line in SHA256SUMS.txt

SHA256SUMS.txt lists every archive in the release, so if you downloaded only one,
add --ignore-missing — a plain -c counts the archives you did not download as
failures.

RunCove v0.4.0

RunCove v0.4.0

RunCove v0.4.0 adds launch groups. A group is a named, ordered set of launch
profiles that starts or stops as one unit, so the set of services you bring up
every morning becomes one button instead of several.

Highlights

• Create as many groups as you need, each with its own name and startup order.
  Members may come from different projects, so one group can bring up a
  database, an API, and a web front end together.
• Whole-group start walks the members in the order you set and waits for each
  one's expected port before moving on, exactly as a single-profile start does.
  A member that is already running counts as started, so pressing Start again
  only fills in what is missing.
• A failed start stops before the next member and keeps everything that already
  started. The message names the member it stopped at, says how many started
  before it, and offers the same View occupant action as a single-profile
  port conflict.
• Whole-group stop walks the members in reverse, and a member it cannot stop
  does not stop the rest. The report counts every failure and names the first.
• Each group shows its startup order and whether it is fully running, partly
  running, or not running. Deleting a launch profile removes it from every group
  that used it.

Fixed

• Process stop and exit messages now follow the interface language. A Simplified
  Chinese interface no longer shows English sentences such as Stopped by user
  in the status toast or the log drawer.
• Fields in the project editor keep their own names once validation errors
  appear, so a screen reader no longer announces Program This field is required. as a field's name.
• Saving an existing project records the time it was saved rather than the time
  it was first added.

Upgrade Note

The desktop database migrates to schema version 3 on first launch to store
launch groups — from version 2 if you are coming from v0.3.0, and through
version 2 if you are coming from an older release. Each migration runs in one
transaction and stays at the previous version if it fails, but a successful
upgrade has no downgrade path: v0.3.0 and earlier cannot open the resulting
version 3 database. Copy runcove.sqlite3 out of RunCove's application-data
directory (%LOCALAPPDATA%\com.abysswhale.runcove\) before launching v0.4.0 if
you may need to return to an earlier version.

Known Limitations

• A launch group starts and stops only when you press its button. There is no
  start-at-login and no automatic project startup, by design.
• In the rare case that a run log archive's final buffered flush fails, the
  archive line count can over-report which buffered line reached disk. The byte
  count is measured from the file, and normal writes are unaffected.

Downloads

• runcove-desktop-windows-x86_64-portable.zip contains the unsigned Windows
  desktop application.
• runcove-cli-* archives contain the cross-platform runcove CLI and a
  compatibility executable for existing scripts.
• SHA256SUMS.txt contains SHA-256 checksums for every binary archive.

Windows SmartScreen may show an unknown-publisher warning because the desktop
executable is not code-signed. Download it only from this GitHub release and
verify the archive against SHA256SUMS.txt. Microsoft Edge WebView2 Runtime is
required and is included with current Windows 11 systems.

RunCove v0.3.0

RunCove v0.3.0

RunCove v0.3.0 adds an optional persistent archive for managed-session logs.
The archive is off by default, stays inside RunCove's local application data,
and does not change the existing in-memory log or process-safety model unless
you explicitly enable it.

Highlights

• Enable Archive run logs from the log drawer for future runs. RunCove does
  not backfill output from a session that was already running.
• Reopen archived stdout and stderr from run history. The viewer starts at the
  tail and loads earlier records in bounded pages.
• See whether an archive is writing, finalizing, complete, partial, or removed,
  together with its line count, size, and any dropped output.
• Delete an archive after confirmation while retaining its run-history entry.
• Keep disk use bounded at 10 MiB per session and 200 MiB in total. RunCove
  reclaims the oldest finished archives first and never evicts one still open.

Reliability And Privacy

• A bounded background queue prevents archive I/O from slowing the child
  process. If output arrives too quickly, the dropped lines and bytes are
  reported instead of silently disappearing.
• Startup recovery repairs interrupted rows and accounts for existing files.
  Archive paths are restricted to RunCove-generated names inside its dedicated
  archive directory; links and Windows reparse points are not followed.
• Archive initialization failure does not stop port scanning, project launch,
  process control, or the existing in-memory log drawer.
• Archived output is not filtered. A service can print credentials, tokens,
  personal data, or other sensitive content, so enable archiving only when that
  local persistence is appropriate. RunCove uploads no archive data.

Upgrade Note

The desktop database migrates from schema version 1 to version 2 on first
launch. The migration itself is transactional, but a successful upgrade has no
downgrade path: RunCove v0.2.1 cannot open the upgraded database. Back up the
RunCove application-data directory before launching v0.3.0 if you may need to
return to v0.2.1.

Known Limitations

• In the rare case that the final buffered flush fails, the archive line count
  can over-report which buffered line reached disk. The byte count is measured
  from the file, and normal writes are unaffected.
• Process stop and normal-exit messages produced by the backend remain English
  when the interface language is Simplified Chinese.

Downloads

• runcove-desktop-windows-x86_64-portable.zip contains the unsigned Windows
  desktop application.
• runcove-cli-* archives contain the cross-platform runcove CLI and a
  compatibility executable for existing scripts.
• SHA256SUMS.txt contains SHA-256 checksums for every binary archive.

Windows SmartScreen may show an unknown-publisher warning because the desktop
executable is not code-signed. Download it only from this GitHub release and
verify the archive against SHA256SUMS.txt. Microsoft Edge WebView2 Runtime is
required and is included with current Windows 11 systems.

RunCove v0.2.1

RunCove v0.2.1

RunCove v0.2.1 makes the Windows local-development runtime center easier to
understand and diagnose. The distribution includes the Windows desktop app,
the cross-platform runcove CLI, and a compatibility executable for existing
scripts.

Highlights

• Review the five most recent managed sessions on Overview, or search and
  filter up to 200 stored run-history records in the history drawer.
• Jump from an expected-port conflict to the exact TCP or UDP listener after a
  fresh snapshot check, without automatically terminating another process.
• See explicit saved-root discovery states, retry failed scans, and keep
  candidates available until they are reviewed or successfully imported.
• Copy launch profiles, validate project fields before saving, and copy PID,
  executable-path, or command-line details directly from the Ports view.
• Use expanded English and Simplified Chinese help for run history, conflicts,
  restore failures, project discovery, and the non-persistent log boundary.

Security Boundaries

• Administrator monitoring is deliberately read-only. It improves process
  visibility but disables project launch, stop, restart, restore, browser,
  folder, and external-termination actions so user-controlled commands never
  execute with administrator rights.
• External process termination revalidates the listener, PID, process start
  time, executable path, and managed ownership immediately before using the
  Windows system taskkill.exe.
• Project commands remain structured as program, args[], and cwd; logs are
  bounded in memory and are not persisted by default.
• Existing SQLite data remains compatible. No schema migration is introduced,
  and raw polling snapshots are not persisted.

Downloads

• runcove-desktop-windows-x86_64-portable.zip contains the Windows desktop
  application.
• runcove-cli-* archives contain the runcove CLI and a compatibility
  executable for existing scripts.
• SHA256SUMS.txt contains checksums for every binary archive.

The Windows desktop executable is portable and unsigned. Windows SmartScreen
may show an unknown-publisher warning. Verify the archive against
SHA256SUMS.txt and download it only from this GitHub release. Microsoft Edge
WebView2 Runtime is required and is included with current Windows 11 systems.

The previous v0.2.0 release and the original v0.1.0 tag and release remain
available unchanged.

RunCove v0.2.0

RunCove v0.2.0

RunCove turns the original port-only repository into a Windows-first local
development runtime center. The distribution includes the runcove CLI and a
compatibility executable for existing scripts.

Highlights

• Monitor active TCP and UDP listeners with PID, process, executable, command,
  binding, and trusted project association details when Windows permits them.
• Discover npm and pnpm projects, review structured launch profiles, and keep
  expected ports together with each project.
• Start, stop, and restart managed process trees, inspect bounded in-memory
  logs, detect conflicts, and restore the profiles that were running before the
  previous explicit exit.
• Use the native title-bar close choice and system tray without losing managed
  service state. Launching RunCove again now restores an existing hidden window.
• Use the built-in English and Simplified Chinese help guide for the main
  workflows and safety boundaries.

Security Boundaries

• Administrator monitoring is deliberately read-only. It improves process
  visibility but disables project launch, stop, restart, restore, browser,
  folder, and external-termination actions so user-controlled commands never
  execute with administrator rights.
• External process termination revalidates the listener, PID, process start
  time, executable path, and managed ownership immediately before using the
  Windows system taskkill.exe.
• Project commands remain structured as program, args[], and cwd; logs are
  bounded in memory and are not persisted by default.

Downloads

• runcove-desktop-windows-x86_64-portable.zip contains the Windows desktop
  application.
• runcove-cli-* archives contain the runcove CLI and a compatibility
  executable for existing scripts.
• SHA256SUMS.txt contains checksums for every binary archive.

The Windows desktop executable is portable and unsigned. Windows SmartScreen
may show an unknown-publisher warning. Verify the archive against
SHA256SUMS.txt and download it only from this GitHub release. Microsoft Edge
WebView2 Runtime is required and is included with current Windows 11 systems.

The original v0.1.0 tag and release remain unchanged.

v0.1.0

Full Changelog: https://github.com/AbyssWhalen/portpeek/commits/v0.1.0