langchain-ai/helm
1
0
Fork 0
mirror of https://github.com/langchain-ai/helm.git synced 2026-07-25 04:56:50 -04:00
Code Issues 24 Packages Projects Releases 10 Wiki Activity

[PR #683] [CLOSED] Merge v14-stable into main #681

New Issue
Closed
opened 2026-06-05 19:17:23 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 19:17:23 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/helm/pull/683
Author: @langchain-infra
Created: 4/17/2026
Status: ❌ Closed

Base: main ← Head: v14-stable

📄 Description

Summary

Merges the v0.14 release line (v14-stable) back into main. This brings 7 commits that have accumulated on the stable branch since it diverged.

Commits being merged

  • acf2ad3 chore: remove feedback migration jobs and configurations (#682)
  • c7ff8ae fix: use sync waves to run migrations before app rollout (#677)
  • 56e62ca fix: add missing microsoftOAuthProvider mapping (#672) (#681) — already on main as #672, expect a conflict/no-op here
  • a158ffa chore: bump appVersion and image tags to 0.14.1rc2 (#680)
  • 6d8f3f6 chore: bump appVersion to 0.14.1rc1 (#678)
  • 5418d7a added .Values.commonEnv to hostBackend
  • 26757d0 chore: release self-hosted 0.14.1

Notes

  • main is currently on the 0.13.x line; merging this promotes appVersion to 0.14.1rc2.
  • The microsoftOAuthProvider fix was backported to v14-stable as #681 but originated on main as #672 — Git should resolve this cleanly, but flagging it so reviewers know it's a duplicate.
  • Overall diff: 30 files, +59 / -410 (net -351) driven by the feedback-migration template + config removal.

Test plan

  • Review merge strategy (merge commit / rebase-and-merge / squash) — merge commit preferred to preserve v0.14 history
  • helm lint charts/langsmith passes on the merged result
  • helm template against all ci/*.yaml fixtures renders without errors
  • Confirm no downstream consumers still reference feedbackDataMigration / feedbackConfigMigration

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/helm/pull/683 **Author:** [@langchain-infra](https://github.com/langchain-infra) **Created:** 4/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `v14-stable` --- ### 📄 Description ## Summary Merges the v0.14 release line (`v14-stable`) back into `main`. This brings 7 commits that have accumulated on the stable branch since it diverged. ### Commits being merged - `acf2ad3` chore: remove feedback migration jobs and configurations (#682) - `c7ff8ae` fix: use sync waves to run migrations before app rollout (#677) - `56e62ca` fix: add missing microsoftOAuthProvider mapping (#672) (#681) — already on main as #672, expect a conflict/no-op here - `a158ffa` chore: bump appVersion and image tags to 0.14.1rc2 (#680) - `6d8f3f6` chore: bump appVersion to 0.14.1rc1 (#678) - `5418d7a` added .Values.commonEnv to hostBackend - `26757d0` chore: release self-hosted 0.14.1 ### Notes - `main` is currently on the 0.13.x line; merging this promotes `appVersion` to `0.14.1rc2`. - The microsoftOAuthProvider fix was backported to v14-stable as #681 but originated on main as #672 — Git should resolve this cleanly, but flagging it so reviewers know it's a duplicate. - Overall diff: 30 files, +59 / -410 (net -351) driven by the feedback-migration template + config removal. ## Test plan - [x] Review merge strategy (merge commit / rebase-and-merge / squash) — merge commit preferred to preserve v0.14 history - [x] `helm lint charts/langsmith` passes on the merged result - [x] `helm template` against all `ci/*.yaml` fixtures renders without errors - [x] Confirm no downstream consumers still reference `feedbackDataMigration` / `feedbackConfigMigration` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 19:17:23 -04:00
yindo closed this issue 2026-06-05 19:17:24 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/helm#681
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?