Repository navigation
chore: merge main into feat/alert-batch9 - #704
Merged
Merged
Conversation
Point the install snippets at the current pub.dev releases: flashcat_flutter_plugin ^0.2.0, flashcat_tracking_http_client ^0.1.2 and flashcat_webview_tracking ^0.1.1. The plugin moved to 0.2.0, which a ^0.1.x caret constraint does not admit, and the two add-on packages were republished to depend on it.
docs(rum): bump Flutter SDK snippets to 0.2.0
flashcat_flutter_plugin 0.2.0 exposes the remote configuration channel of the native Android and iOS SDKs to Dart. Add a Remote configuration section to the Flutter advanced configuration page covering remoteConfigurationEnabled, getRemoteConfig(), beforeSampling, setForcedSession() and the add-to-app case, and list Flutter among the platforms the console's Remote Configuration tab supports.
…nd alert webhook detail_url - developer/cli: incident list / incident similar default structured projections now include num and detail_url (flashduty-cli internal/cli/incident.go) - on-call/integration/webhooks/alert-webhook: add the detail_url row to the Alert payload table (fc-event structs.AlertItem + logic.AlertDocToItem)
docs: doc-review 2026-09-28 (diff) — CLI incident projection fields and alert webhook detail_url
Deployments, deployment statuses and releases from a GitHub webhook become Flashduty changes: one change per deployment id or release id, with the state-to-status mapping, ignored deliveries, labels and FAQ. Adds the zh/en pages, the navigation entries and the GithubChange in-app doc key.
change_status now accepts Failed. Like Done and Canceled it is a terminal status: the event time is recorded as the change end time. Update the standard change event docs, the change search view, and the change_status enum in the OpenAPI specs.
docs(change): document the Failed change status
docs(change-integration): GitHub change integration
Documents the GitLab deployment change integration: webhook setup with Deployment events, deployment status mapping, what one change is, labels and FAQ.
docs: add HCP Terraform change integration page
Argo CD Notifications webhook service, template and trigger that record each Application sync operation as a Flashduty change, with the phase-to-status mapping, the change key and the label reference.
…eat/netlify-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
…eat/gitlab-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
…eat/argocd-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
docs(change): add Argo CD change integration
…eat/netlify-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
…eat/gitlab-change # Conflicts: # docs.json
…eat/jfrog-artifactory-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
docs(change): add Netlify change integration page
docs(change): add GitLab change integration page
…eat/vercel-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
…eat/jfrog-artifactory-change # Conflicts: # docs.json # integration-docs/src/doc-map.mjs
release: 11 new alert integrations (batch 5)
release: 10 new change integrations
Both schemas return a console page URL for the alert
(`{console}/alert/detail/{alert_id}`), empty when the deployment has
no console base configured. Add the field to en and zh specs.
api: document detail_url on AlertInfo and AlertItem
chore: merge main into feat/alert-batch7
…inders The alert notification settings use a Custom action checkbox with a script list, and reminders are enabled with Set reminders. The script upload button is Add a script.
docs(cfengine): match Mission Portal labels for custom action and reminders
release: 9 new alert integrations
docs(ghost-inspector): match the real notification settings UI
chore: merge main into feat/alert-batch6
release: 11 new alert integrations (batch 6)
docs(wormly): document Send Test behavior and correct contact button label
chore: merge main into feat/alert-batch8
…updates do not re-open the alert
…losed docs(gitguardian): critical and info severities; updates on closed incidents
docs(tideways): correct notification setup steps and recovery behavior
…r UI GitGuardian: webhook is created per team from Destinations, with Configuration and Events tabs; the status events sit under Incident status change; Send test message is in the row menu. LogRocket: alerts are created from a saved Timeseries chart via Alerts, Create Alert; reason carries the alert name.
…alert-e2e docs(alert): match GitGuardian and LogRocket setup steps to the vendor UI
…est notification behavior The editor's test button is Send Test Notification (in the webhook action) and posts the all-zero UUID as alert_rule_id. Metric names, time window range and the Body field label follow the current UI.
docs(alert-integration): LangSmith UI labels and test notification
Alert integrations batch 8: Auvik, Tideways, NS1 Connect, Wormly, Kuvasz, Circonus, Dash0, GitGuardian, LogRocket, LangSmith
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Merge of origin/main into the batch integration branch so the promotion PR to main contains this batch only. Conflicts: list-append only, both sides kept.