[editorial] Anchor IDs do not exist in v1.27 of docs

[chalin]

• Context: Add support for database batch operations #1072
  There are two occurrences of links with the following URL: /docs/database/database-spans.md#batch-operations, but that anchor ID doesn't exist. What did you have in mind as a target @trask?
• Context: Revamp messaging metrics to support generic operations #1006
  There are two occurrences of links with the following URL: /docs/messaging/messaging-spans.md#common-messaging-operations, but that anchor ID doesn't exist. What did you have in mind as a target @lmolkova?

---

These issues were reported by the link checker via the GitHub action checks of:

• Update semantic-conventions version to v1.27.0 opentelemetry.io#4938

In particular, see the "hash does not exist" errors reported in: https://github.com/open-telemetry/opentelemetry.io/actions/runs/10218743437/job/28275657390?pr=4938

[lmolkova]

Thanks @chalin !

Is there a way we can easily test it before releasing? I.e. can we somehow trigger docs pipeline for a specific commit in the semconv repo?

We used to have cross-file link checker, but it's gone and we have no replacement for it across all repos - #1009.

[chalin]

The easiest way that I can think of, would be to build the OTel website using the pre-release commit of this repo. We could define a manually triggered workflow that could build the OTel website using main@HEAD, which could be run just before putting out the release. /cc @open-telemetry/docs-maintainers

I suppose that the same workflow could be run via a cron job over main@HEAD, but that might report more errors than it's worth? Maybe not.

[chalin]

Related:

• [editorial] Fix invalid #instrument-advice anchors #1316