Specfold v1.9.1

Specfold v1.9.1

Changed

• Postman and compatible source variables are no longer turned into a new environment automatically during import.
• The Import screen now offers Import source variables as a new environment for collections that need tokens, client IDs, or other reusable values.
• Choosing that option adds a separate source environment but keeps the currently active environment selected.
• Imported Postman baseUrl values continue to live at collection scope, so route resolution works without copying the value into an environment.
• Import completion explains when source variables were intentionally not added.

Security

• Sensitive source variables are only written to the local environment store after the user explicitly opts in to importing them.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Automatic download and installation of updates remain intentionally excluded.
• Imported scripts are not executed.

Verification

• Source-size checks, ESLint, typecheck, the full automated test suite, production build, platform packages, and SHA-256 checksums pass on the final release commit.

Specfold v1.9.0

Specfold v1.9.0

Added

• The Environment screen now includes a lightweight Test connection action. A reachable HTTP endpoint reports success even when it intentionally requires authentication or does not support HEAD.
• Responses can switch between Raw JSON and Pretty JSON, search response content, copy matching response text, and copy error details without selecting text manually.
• Frequently used requests can be pinned to the top of their folder. The global request search shortcut is Ctrl/Cmd+K.
• Import completion now reports the number of imported requests and folders.
• Settings show the local data location, automatic safety-backup information, and an Open data folder action.
• A concise first-run guide explains the import, route, and send workflow.

Changed

• Environment base URLs are now edited only in Environment. Changing an environment default never replaces a collection or folder override.
• The Base URL routing view makes the scope explicit: an environment default, a collection override, or the nearest folder override. This keeps separate proxy routes isolated in one collection.
• Request and response workflows retain their adjustable horizontal layout and response text-size controls while adding a clearer response inspection path.
• Production TypeScript, TSX, and CSS source files remain under the repository's 500-line source-size limit.

Security

• Connection testing reuses the configured timeout, proxy, and TLS settings and does not persist credentials or response content.
• Local data and backup locations are exposed only through an explicit user action in Settings.
• Automatic update downloads and installation remain intentionally excluded; update checks link to GitHub Releases.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Install v1.9.0 manually from GitHub Releases after verifying the published checksum.
• SOCKS proxies, browser-based OAuth login, remote $ref fetching, and imported script execution are not included.

Verification

• Source-size checks, ESLint, typecheck, 173 automated tests, production build, platform packages, and SHA-256 checksums must pass on the final release commit.

Specfold v1.8.0

Specfold v1.8.0

Added

• Native File, Edit, View, Window, and Help menus expose Import, Export, Settings, About, update checks, documentation, and release notes.
• The request and response panels now use an accessible horizontal divider that supports pointer dragging, keyboard resizing, and double-click reset.
• Response body, header, and raw views have persistent A−/A+ text sizing from 11 px to 18 px.
• A response field can be saved as a folder access token. The value remains an encrypted environment secret while the folder stores only its variable name.
• Bearer requests can apply the nearest inherited folder token through Use folder token.

Changed

• Import, Export, Environments, Settings, and About are lazy-loaded. The initial renderer bundle is split into focused application, React, icon, and core chunks.
• Storage validation was separated from persistence, and production source files remain below 500 lines.
• ESLint is now part of the local and CI release gate.
• Electron was updated to 43.2.0 and Undici to 8.9.0.
• README, architecture, product, UI, and import/export documentation now describe folder-scoped token workflows and the resizable editor.

Security

• Packaged renderer assets use the bounded specfold://app protocol instead of file://.
• Renderer navigation and new windows are denied; permissions default to denied.
• IPC calls validate the trusted main frame and bound runtime payload shapes and sizes.
• External navigation is restricted to approved HTTPS GatewayLabs and GitHub destinations.
• Folder access-token variables are encrypted at rest even if their environment secret flag was manually disabled.
• Automatic update download and installation remain intentionally excluded.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Install v1.8.0 manually from GitHub Releases after verifying the published checksum.
• SOCKS proxies, browser-based OAuth login, remote $ref fetching, and imported script execution are not included.

Verification

• Source-size checks, ESLint, typecheck, 164 automated tests, production build, platform packages, and SHA-256 checksums must pass on the final release commit.

Specfold v1.7.1

Specfold v1.7.1

Changed

• About now opens from the application top bar instead of occupying space in Settings.
• The About experience is an accessible dialog with a close button, backdrop close, Escape-key support, and initial keyboard focus.
• Settings can now use up to 960 px of content width and still collapses to a single responsive column on narrow windows.
• Product version, platform, architecture, license, release links, download links, and manual update checks remain available in About.

Security

• Update checks remain read-only GitHub Release metadata requests.
• Automatic package downloads, installer launches, and update installation are not included.
• External links continue to be opened through the main process and are limited to http and https.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Install v1.7.1 manually from GitHub Releases after verifying the published checksum.
• SOCKS proxies and browser-based OAuth login are not included.

Verification

• Source-size checks, typecheck, automated tests, production build, platform packages, and SHA-256 checksums must pass on the final release commit.

v1.7.0

Specfold v1.7.0

Added

• Settings -> About now shows the installed Specfold version, platform, architecture, license, current release link, and download page.
• Manual update checking now compares the installed version with the latest GitHub Release and reports whether a newer version is available.
• Update results provide release notes and download links without downloading or installing anything automatically.

Changed

• The main workspace header no longer repeats the Specfold logo and product name.
• The active environment selector is now a compact one-line control in the top bar.
• The About panel is now the dedicated place for product identity and version information.

Security

• Update checks are read-only GitHub Release metadata requests.
• Automatic package download, automatic installer launch, and auto-update installation are intentionally not included.
• External links are opened through the main process and limited to http and https URLs.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Automatic update download and installation are not included; install v1.7.0 manually from GitHub Releases.
• SOCKS proxies and browser-based OAuth login are not included.

Verification

• Source-size checks, typecheck, automated tests, production build, platform packages, and SHA-256 checksums must pass on the final release commit.

v1.6.0

Specfold v1.6.0

Added

• Compact, Default, and Large text-density preferences, persisted with the rest of the local application settings.
• A concise resolved-route summary that identifies the effective base URL and whether it came from the environment, collection, or nearest folder.

Changed

• The request editor now sits above the response inspector so both use the full available width.
• Compact text density is the default for a clearer, denser desktop workspace.
• Base URL controls use a simpler two-part layout: editable scope and resolved route.

Fixed

• Requests with an inherited base URL no longer report that baseUrl is missing when the value is supplied by their environment or folder hierarchy.
• Empty or whitespace-only collection base URLs no longer hide a valid environment base URL.
• Route previews always use the active request's real folder chain, even when another tree row was selected previously.

Security

• No security model changes. Local-first storage, encrypted secret persistence where supported, and session-only upload grants remain unchanged.

Known limitations

• Release packages are not yet code-signed, and macOS packages are not notarized.
• Auto-update is not included; install v1.6.0 manually from GitHub Releases.
• SOCKS proxies and browser-based OAuth login are not included.

Verification

• Source-size checks, typecheck, 142 automated tests, production build, platform packages, and SHA-256 checksums must pass on the final release commit.

v1.5.0

Full Changelog: v1.4.0...v1.5.0