[pull] main from hoppscotch:main #82
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#5496) fix: reset ONBOARDING_COMPLETED config to false on reset
…ed (#5494) * fix: graceful shutdown handling for backend app * chore: add startup delay to health check script
v2025.10.0 --------- Co-authored-by: jamesgeorge007 <[email protected]>
Add per-domain toggle to disable automatic HTTP redirect following in the Native and Agent interceptors. When disabled, requests return the redirect response (status code, headers, body) without following the Location header. Previously HTTP redirects were always followed (on browser, can't do much about that, see https://fetch.spec.whatwg.org/#atomic-http-redirect-handling) without option to inspect the redirect response itself. This prevented developers from accessing redirect metadata needed when testing OAuth flows (PKCE where intermediate responses contain authorization tokens), authentication endpoints that return codes in Location headers with 302 status, and debugging API redirect chains. But on the desktop app, redirects were just never followed, creating the opposite effect. The browser's fetch API applies atomic HTTP redirect handling per spec, making it impossible to intercept redirects and inspect their responses. The Native and Agent interceptors use curl and native HTTP clients respectively, both supporting redirect control, making this feature viable for these specific interceptors. (Proxyscotch tbd).
…lity layer (#5417) Co-authored-by: nivedin <[email protected]>
This replaces the matrix-based Agent build strategy with dedicated platform-specific jobs, synchronizing with the Desktop workflow patterns and preparing for the broader CI/CD updation cycle.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: jamesgeorge007 <[email protected]>
Co-authored-by: jamesgeorge007 <[email protected]>
Co-authored-by: Anwarul Islam <[email protected]> Co-authored-by: jamesgeorge007 <[email protected]>
Added support for overriding the default session cookie name using the `INFRA.SESSION_COOKIE_NAME` config or the `SESSION_COOKIE_NAME` environment variable. This helps compatibility with proxies or load balancers that cannot handle cookie names containing dots. --- Co-authored-by: mirarifhasan <[email protected]> Co-authored-by: jamesgeorge007 <[email protected]>
Co-authored-by: Copilot <[email protected]> Co-authored-by: nivedin <[email protected]> Co-authored-by: jamesgeorge007 <[email protected]>
Node.js `v24` became LTS recently, causing CI failures due to `V8` API incompatibilities with isolated-vm `v5.x`. Pinning to `v22` aligns with our production environment (Alpine `v3.22.1` ships Node.js `v22.16.0`) and ensures build stability. `isolated-vm v6+` will be required for Node.js `v24` support and will be addressed in a future dependency update cycle.
Co-authored-by: nivedin <[email protected]> Co-authored-by: jamesgeorge007 <[email protected]> Co-authored-by: mirarifhasan <[email protected]>
- Fix null/undefined environment variable handling across namespaces
- Fix pm.request console.log output to display properly
- Add pm.request.id and pm.request.name type definitions
- Fix assertion error messages to show actual values
- Strip `export {};` from collection exports and legacy sandbox editor display
…mock servers (#5527) * fix(mock-server): handle null collection case in dashboard display * feat(mock-server): add private access hint for non-public mock servers * fix(mock-server): update private access hint for clarity * refactor(mock-server): remove console logs from mock server creation and update
- Update active state styles for better visibility in the mock server. - BE updates catered to improving content type handling in the mock server. - Introduced a `disableMockServerInPersonalWorkspace` platform-level feature flag. - Remove inactive keyboard shorthand nudges from the Mock server dashboard context menu. --- Co-authored-by: mirarifhasan <[email protected]> Co-authored-by: jamesgeorge007 <[email protected]>
… collections (#5536) Co-authored-by: jamesgeorge007 <[email protected]>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…ept partial objects
The runtime schema uses .catch() fallbacks for all fields (`key`, `value`, `active`, `description`), making them effectively optional at runtime. Updated type definitions to use Partial<> to match actual runtime behavior and prevent type errors in usage.
This allows valid usage patterns like:
``
hopp.request.setHeaders([{ key: "X-Custom", value: "foo" }])
```
Without requiring all fields (`active`, `description`) to be explicitly provided.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
12 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )