Release: v1.1.5 #426
Open
Release: v1.1.5 #426
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
[#380] Track chatbot semantic search costs and performance
Author
Changelog- [#380] Track chatbot semantic search usage metrics [#414] @sahilds1
- Update VITE_API_BASE_URL to point to the new prod url [#429] @TineoC
- sanitizer @AkhilRB0204
- refactor: use relative URLs and centralize API endpoints (closes #431) [#432] @TineoC
- ci: refactor pipelines for continuous deployment to sandbox [#442] @TineoC
- build: use cpu-only torch to reduce image size and fix CI build [#443] @TineoC
- fix(ci): use actions/checkout@v4 instead of non-existent v5 @TineoC
- Update GitHub Sponsors username in FUNDING.yml @sahilds1
- [#187] Add a PR template [#444] @sahilds1
- [#446] BUGFIX: Fix failing local development frontend API calls [#447] @sahilds1
- Fix backend network errors and cleanup dev environment [#460] @TineoC
- fix: deploy API and CI — release-based image tags, version endpoint, prod compose [#455] @TineoC |
Update VITE_API_BASE_URL to point to the new prod url
- Introduced a new `endpoints.ts` file to centralize all API endpoint paths for better maintainability and type safety. - Updated various components and services to utilize the new centralized endpoints, enhancing consistency across the codebase. - Created a comprehensive `API_ENDPOINTS_REFACTORING.md` guide detailing the refactoring process and usage patterns for the new endpoints. - Removed hardcoded URLs in favor of the centralized configuration, improving code readability and reducing the risk of errors.
- Update Django URLs to serve all APIs under /api/ prefix - Change frontend to use relative URLs (empty baseURL) instead of environment-specific domains - Create centralized endpoints.ts for maintainable API URL management - Update all frontend components to use centralized endpoints - Remove all VITE_API_BASE_URL and REACT_APP_API_BASE_URL dependencies - Add helper functions for dynamic endpoints with parameters This ensures the same Docker image works in both production and sandbox environments without requiring environment-specific configuration. Fixes: - Frontend calling old domain (balancer.live.k8s.phl.io) - API calls failing after domain migration - /login and /adminportal pages not working Closes #431
refactor: use relative URLs and centralize API endpoints (closes #431)
ci: refactor pipelines for continuous deployment to sandbox
build: use cpu-only torch to reduce image size and fix CI build
[#187] Add a PR template
[#446] BUGFIX: Fix failing local development frontend API calls
- Add trailing newline to frontend/.env.production (lint) - Clarify apiClient baseURL comment for sandbox/production - Add Frontend: Lint and Build workflow on develop - Add docs/DEPLOY_RESOLUTION_STEPS.md for PR follow-up
- devbox.json: use kind-config.yaml (file exists as .yaml) - deploy/manifests/balancer/overlays/kind: overlay with secretGenerator for balancer-config (SQLite) so kind runs without PostgreSQL - deploy/kind-test.sh: create cluster, install ingress, build/load image, apply kind overlay, wait for deployment, curl API and verify status
…ath" This reverts commit 1b36e6f.
…, manual deploy - Deploy: Downstream: add permissions (contents, actions, pull-requests), add workflow_dispatch target (both|sandbox|live) for manual deploy; CD to sandbox on develop, live on release; manual run opens PRs to cluster repos - Remove frontend/.env.production and VITE_API_BASE_URL from .env (relative URLs) - SPA catch-all: always register, serve index.html at request time or 404 - Docs: README/CLAUDE/MIGRATION/DEPLOY_RESOLUTION_STEPS and PR body
This reverts commit a862760.
Fix backend network errors and cleanup dev environment
fix: deploy API and CI — release-based image tags, version endpoint, prod compose
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Improvements
Technical