-
Notifications
You must be signed in to change notification settings - Fork 1
Bump version v2.10.2 #208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Bump version v2.10.2 #208
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
624996c
feat(EmailOctopus): add pending status option for contact actions
RishadAlam 88921e6
refactor(IntegrationHelpers): remove unused authorization logic and t…
RishadAlam 9df4ec0
feat(SecretInput): add masked input field with reveal toggle function…
RishadAlam bcaf12d
Merge branch 'main' into redesign/settings-doc-support
RishadAlam 21d39ab
refactor(AllTriggersName): remove 'Bit CRM' entry from triggers list
RishadAlam 721cb8e
feat(BitCrm): lock contact and company into convert lead
RishadAlam aa667ef
refactor(BitCrm): trim convert lead comments
RishadAlam f421c8a
feat: bitCrm support custom fields in actions
RishadAlam a45b74e
fix: bitform base url domain key
RishadAlam 5d29b1f
feat(BitCrm): fetch action fields from Bit CRM
RishadAlam be0abd5
feat(BitCrm): set closing date on won/lost stage
RishadAlam 0eef621
feat: enhance prepareFetchFormatFields with label path handling
RishadAlam c542a36
chore: bump version to 2.10.2 and update changelog
RishadAlam 88a6204
fix(BitCrm): resolve plugin check warnings
RishadAlam 91a151d
feat(BitCrm): enhance lead handling and timezone conversion logic
RishadAlam File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two things:
closed_at(L588). Any pre-existingupdate_deal_stageflow that targets a closing stage without a mapped closing date will start failing at run time. This rests on the "shipped in no release tag → no saved flows" assumption from the PR description — please confirm it holds forupdate_deal_stagespecifically.dealStages()returns[]and$definitionisnull;$definition['deal_category'] ?? ''silently yields'', so the closing-date requirement is skipped. That's the intended fallback but it's implicit — a one-line comment would prevent a future "why doesn't this validate" head-scratch.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Right to push on it — the assumption does not hold.
update_deal_stageshipped in 2.10.1 (released 30 Jul 2026):git show 2.10.1:frontend/src/components/AllIntegrations/BitCrm/staticData.jscarries it at line 47, andbackend/Actions/BitCrm/is present in that tag. Saved flows can exist, so the hard requirement is dropped — an unmapped closing date now leaves the column alone instead of failing a stage change that used to work:closingDateFieldstaysrequired: trueon the frontend, so a flow built or edited from now on is still steered to map it — only the run-time hard stop is gone. The PR description's "shipped in no release tag" line will be corrected too.2. Comment added:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correcting my previous reply on point 1 — the hard requirement stays. A won or lost stage without a closing date is not a state worth writing, so the action fails rather than closing a deal with no closing date on it:
The finding behind your question still stands and the PR description will be corrected:
update_deal_stagedid ship in 2.10.1 (released 30 Jul 2026 —backend/Actions/BitCrm/is in the tag, andstaticData.js:47carries the action). Itsupdate_deal_stageoffered onlydeal_id, so no 2.10.1 flow can have a closing date mapped, and any of them pointed at a won or lost stage will now fail until the flow is opened and the row filled in. That is accepted deliberately rather than by assumption.Point 2 is addressed as asked: