docs: fix CHANGELOG conflict marker and document rand security fix

Open Beginner friendly
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
documentation

Research direction

Inspect CHANGELOG.md and docs/dependencies.md, starting with the [Unreleased] section and the existing dependency graph and per-file changelog table. Done means the stale conflict marker is gone, the rand security update and RUSTSEC-2026-0097 are documented, rand and its sub-crates appear under transitive dev dependencies, and the date and version label are updated.

Written by the indexing model from the issue text.

Description

agentic-workflows automation documentation

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: CHANGELOG.md

Summary

Two documentation issues found after the fix(security): update rand to 0.9.3 (RUSTSEC-2026-0097) commit:

1. Leftover merge conflict marker in CHANGELOG.md

A >>>>>>> 28aebca (feat(release): adopt attested delivery pipeline) conflict marker was left unresolved in the [Unreleased] section. Removed.

2. Security fix not recorded in changelog or dependency reference

The rand crate was updated (transitively via proptest) to remediate [RUSTSEC-2026-0097]((rustsec.org/redacted), but no changelog entry existed.

Changes

  • CHANGELOG.md: Remove stale >>>>>>> conflict marker; add ### Security entry for rand 0.9.4 / RUSTSEC-2026-0097.
  • docs/dependencies.md:
    • Add rand under a new Transitive Dev Dependencies section (pulled in by proptest).
    • Expand dependency graph to show rand and its sub-crates under proptest.
    • Add a row to the per-file changelog table for the 2026-06-12 security update.
    • Update Last Updated date and version label.

Generated by Update Docs · 336.6 AIC · ⌖ 14.5 AIC · ⊞ 34.9K ·

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/update-docs.md@adea00ee5830135f24022f1000d706c7f5fa24c4

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 27437146327 -n agent -D /tmp/agent-27437146327

# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-27437146327/aw-docs-fix-changelog-and-dependencies-rand-security.bundle refs/heads/docs/fix-changelog-and-dependencies-rand-security:refs/bundles/create-pr-docs-fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76-bce9c7df
git update-ref refs/heads/docs/fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76 refs/bundles/create-pr-docs-fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76-bce9c7df
git checkout docs/fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-docs-fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76-bce9c7df

# Push the branch to origin
git push origin docs/fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76

# Create the pull request
gh pr create --title 'docs: fix CHANGELOG conflict marker and document rand security fix' --base main --head docs/fix-changelog-and-dependencies-rand-security-ddbbe41eb0af1a76 --repo zircote/adrscope
Dominant language
Rust
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zircote/adrscope

All issues in zircote/adrscope

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.