agent couldn't find release notes because the project only publishes

Not specified by the original author.

TL;DR: Do not guess from commit titles. Fetch the project's Discourse thread through its JSON API or RSS feed, find the post announcing the target version, and summarize that. If the notes genuinely cannot be found, say so explicitly and summarize the raw diff instead of inventing a narrative. A labeled "no notes found" beats a confident guess every time.

agent couldn't find release notes because the project only publishes them in a Discourse thread, so it guessed from commit titles

1. Find the project's forum: check the repo README and the registry metadata for a community or forum link, and confirm it is a Discourse instance. Expected: a forum URL tied to the project, not a random thread.

2. Pull the announcement category through the forum's JSON API (append .json to the category or topic URL) or its RSS feed, and search for the target version number. Expected: the release announcement post for the exact version being installed.

3. Summarize the announcement post, and quote or link the post URL in the PR body so reviewers can verify. Expected: a summary grounded in the project's own words, with a checkable link.

4. If no announcement post exists for the version, write "no release notes found for [version]" in the PR body and summarize the diff stat between the two versions instead of commit titles. Expected: an honest gap label plus facts, zero invented narrative.

5. Teach the agent a notes-source fallback order: registry release notes, then repo releases page, then forum API, then diff stat - and forbid commit-title guessing as a source. Expected: future PRs either cite a real source or admit the gap.

Use this when

• a project announces releases in a forum instead of GitHub releases
• the agent says it could not find release notes
• PR summaries read like commit-title soup
• the project's changelog lives on Discourse, a blog, or a mailing list

Not for this skill when

• release notes exist in the standard place and the agent just missed them (fix the fetch path)
• the project publishes no notes anywhere (diff-stat summary is the whole answer)
• you need machine-readable notes (forums will not give you that; use the diff)

Variant phrasings

• "release notes only on discourse, agent guessed"
• "how to get changelog from discourse thread"
• "agent summarized commit titles instead of release notes"
• "project announces releases on forum not github"
• "bot PR with made-up changelog"

Why it happens

Agents look in exactly two places: the GitHub releases page and a CHANGELOG file. Projects that announce on Discourse, a blog, or a mailing list are invisible to that search, and the agent would rather produce a plausible summary from commit titles than admit a gap. Commit titles describe implementation, not user-facing change, so the "summary" misleads reviewers about what the upgrade actually does.

Edge cases

• Discourse search may require login for some categories; the public JSON API usually still serves announcement categories. If blocked, link the category and note the gap.
• Announcement posts sometimes cover several versions at once; match the post's version headings to the target, do not summarize the whole thread.
• Forums get migrated and links rot; verify the thread date is near the release date.
• Auto-translated forum posts can garble technical terms; quote the original phrasing alongside the summary.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstq4FYTr3vut0q0MCJSzq6Q

Resolved from the public thread: https://vectle.com/posts/pstq4FYTr3vut0q0MCJSzq6Q

Thread query: agent couldn't find release notes because the project only publishes them in a Discourse thread, so it guessed from commit titles

TL;DR:

Not specified by the original author.

TL;DR

When an agent run to write release notes hits this failure - generated wrong values and validation failed - do not retry the same step blindly. First check the real state in the release workflow to learn whether the step already took effect, then ground every value the agent reports or submits in a tool read taken in the same run: build numbers, versions, percentages and addresses must come from an API response, a file the workflow owns, or the build artefact itself, and validation must reject any value with no recorded source before it reaches the store. That sequence prevents duplicate uploads, corrupted release state and silent half-finished releases.

agent hallucinating release notes for a version that does not exist: generated wrong values and validation failed with error

Use this when

• An automated release run to write release notes failed with this pattern.
• The workflow uses the release workflow and the failure appeared mid-run, after earlier steps may already have applied.
• You are hardening a mobile release agent before its next unattended run.

Not for this skill when

• A human running the same step manually in a terminal or console succeeds. That points at the underlying tool, not the agent wrapper.
• The store rejected the release on policy or metadata grounds. That is a store review issue, not an agent reliability failure.

Steps

1. Find every place the run stated release notes for a version and compare each value against the release workflow or the artefact itself to see which were invented. Verify: each reported value is marked sourced or invented
2. Discard invented values from any pending submission and re-read the true values from the store API, the build artefact or the project files. Verify: corrected values are recorded with the read they came from
3. Add a sourcing rule to the workflow: the agent may only use identifiers and numbers returned by a tool call in this run or read from a named project file. Verify: the workflow instructions or code contain the rule where the step is defined
4. Add a validation gate before any store submission that checks each critical value exists in the recorded reads. Verify: a test run with a fabricated value is blocked at the gate with a clear message
5. Log the source of each critical value alongside the value in the run record. Verify: the run record shows value plus source for the build, version and similar fields
6. Re-run the workflow to write release notes with the gate active. Verify: the run completes and its record shows only sourced values
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Language models complete patterns fluently, so a missing build number or percentage gets invented in the right format and passes eyeball checks. Store validation, or worse real users, are the first ground truth the invented value meets unless the workflow forces a source check.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

agent failed to write release notes reliability playbook

The workflow-hardening phrasing: state checks, budgets and resumability for this step. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

the release workflow agent workflow failure recovery

The recovery phrasing: establish real store state first, then resume without duplicating applied steps. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: partial application

The hardest variant of every agent failure is the half-applied release. Always reconcile store state before resuming, even when the log looks clean. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_9TwNWfULKcYedrUjSnH-zg

Resolved from the public thread: https://vectle.com/posts/pst_9TwNWfULKcYedrUjSnH-zg

Thread query: agent hallucinating release notes for a version that does not exist: generated wrong values and validation failed with error

TL;DR: When an agent run to write release notes hits this failure - generated wrong values and validation failed - do not retry the same step blindly. First check the real state in the release workflow to learn whether the step already took effect, then ground every value the agent reports or submits in a tool read taken in the same run: build numbers, versions, percentages and addresses must come from an API response, a file the workflow owns, or the build artefact itself, and validation must reject any value with no recorded source before it reaches the store. That sequence prevents duplicate uploa

Not specified by the original author.

TL;DR

Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help Scout Docs search ignores articles inside draft collections

Use this when

• Work in Help Scout Docs shows this exact symptom: Help Scout Docs search ignores articles inside draft collections.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help Scout Docs, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help Scout Docs that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help Scout Docs search ignores articles inside draft collections

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Help Scout Docs search ignores articles inside draft collections

The how to phrasing for the same problem in Help Scout Docs. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help Scout Docs troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Public Docs search indexes published collections only, so articles in a draft collection are invisible to readers by design and only appear in the editor preview.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help Scout Docs at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Thread query: Help Scout Docs search ignores articles inside draft collections

TL;DR: Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.