Skip to content

FreqMapper v1.0.1

Summary

Shared trip links now open on the correct public site, while reviewed releases publish complete Discord announcements only after approval. Release notes remain consistent across Help, GitHub, and Discord, and the announcement keeps as much useful detail as Discord can safely display.

What's new

  • GitHub releases now begin as drafts after the exact production commit passes deployment verification. A person can read and correct the complete release before choosing Publish release.
  • Publishing the reviewed GitHub draft unlocks the Discord notification. Until that approval happens, the releases channel and servers following it receive nothing.
  • The FreqMapper bot now publishes its release message as an announcement, allowing servers that follow the channel to receive the same approved update automatically.

Improvements

  • Discord announcements now carry the descriptive version title, affected product areas, production revision, and readable release date.
  • Each announcement includes the complete summary, what's new, improvements, fixes, affected areas, required action, mobile availability, and known limitations whenever they fit within Discord's 6,000-character embed limit.
  • Longer announcements are packed as close to Discord's limit as complete paragraphs, bullets, and words allow. The renderer avoids cutting a bullet in the middle and links to the complete Help page only when the source genuinely exceeds the limit.
  • AI-generated drafts now ask for every supported user-visible detail while explicitly rejecting filler, repetition, speculation, and invented claims. A human must still review and approve every statement before merge.
  • Release-only tooling and internal process changes can use release:none, but validation now rejects that label whenever a pull request also changes production behavior.
  • Recovery checks distinguish between a missing Discord message, a message that still needs to be published, and a draft GitHub release that still needs approval, reducing the chance of duplicate announcements.

Fixes

  • Copied shared-trip links no longer inherit the private development hostname and port. Standard deployments now direct those links to the public FreqMapper trip page, while deployments with a separate public trip hostname can configure it explicitly.
  • Release notes that fit within Discord's full embed allowance are no longer shortened unnecessarily or replaced by an early “See the full release notes” message.
  • Announcement titles and truncation links now open the matching public Help release page instead of sending readers to the developer-facing GitHub release.

What you need to do

Most people do not need to do anything. Shared links created after this update use the correct public site automatically.

Release managers must review the draft GitHub release and click Publish release before Discord is notified. Operators using a custom public hostname specifically for shared trips can set that hostname in the deployment configuration; standard FreqMapper development and production hosts use the safe default automatically.

Mobile availability

No Android or iPhone build is included in this release. Existing supported app versions continue to create, copy, and revoke shared-trip links through the server.

Known limitations

Discord permits no more than 6,000 total embed characters. When reviewed notes exceed that limit, the announcement includes as much complete text as possible and links to the unabridged Help page.

AI can prepare a factual first draft from pull-request evidence, but it cannot confirm real-world availability or unsupported claims. Human review remains required before the release note can pass validation or be published.