ForgeRock
Team
forgerock
Sign in / Sign up
Open main menu
forgerock
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
579
badd4937 fix(ci): filter snapshot slack notification to only released packages Only include packages whose version contains the snapshot tag, so packages in the changeset ignore list (e.g. token-vault) that keep their stable version are excluded from the notification.
16 days ago
by ryanbas21
r
Succeeded
579
89395689 fix(ci): unify slack notifications for snapshot and publish jobs - Snapshot job now reads package.json files to build a real payload instead of hardcoding empty publishedPackages - Both jobs use the same jq-based JSON payload construction - Add warning annotations when Slack notifications fail so failures are visible in the Actions summary without blocking the pipeline
16 days ago
by ryanbas21
r
Failed
579
Generating fix
→
e4ed683d fix(ci): unify slack notifications for snapshot and publish jobs - Snapshot job now reads package.json files to build a real payload instead of hardcoding empty publishedPackages - Both jobs use the same jq-based JSON payload construction - Add warning annotations when Slack notifications fail so failures are visible in the Actions summary without blocking the pipeline
16 days ago
by ryanbas21
r
Succeeded
579
afd9317c fix(ci): unify slack notifications for snapshot and publish jobs - Snapshot job now reads package.json files to build a real payload instead of hardcoding empty publishedPackages - Both jobs use the same jq-based JSON payload construction - Add warning annotations when Slack notifications fail so failures are visible in the Actions summary without blocking the pipeline
16 days ago
by ryanbas21
r
Succeeded
579
83b97b6b fix(ci): fix slack payload parsing and prevent notification failures from blocking CI The release publish workflow failed because the Slack payload contained unescaped multi-line mrkdwn content that broke the webhook action's parser. This caused code coverage to be skipped since the job halted on the Slack error. - Build a proper JSON payload via jq instead of raw string interpolation - Use env vars for changesets output to avoid command injection - Add continue-on-error to Slack steps so notifications never block the pipeline
16 days ago
by ryanbas21
r
Previous page
Previous
Next
Next page