Skip to content

Document date tags for generic IOCs - #273

Merged
gilesknap merged 1 commit into
mainfrom
generic-ioc-date-tags
Oct 5, 2026
Merged

gilesknap merged 1 commit into
mainfrom
generic-ioc-date-tags

Conversation

@gilesknap

@gilesknap gilesknap commented Oct 5, 2026 •

Copy link
Copy Markdown
Member

Adds the date-tag form (2026.9.1) to the generic IOC version naming note, alongside UPSTREAM_VERSIONecN. Matches the DLS developer guide's update-ioc-images how-to.

Part of #269.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HEadCafQcH99QcitezEp8A

Summary by CodeRabbit

  • Documentation
    • Clarified that Generic IOCs without a clear primary support module use date-based release tags, with an example for the first release of September 2026.

Generic IOCs with no clear primary support module are tagged with the
release date (e.g. 2026.9.1) rather than UPSTREAM_VERSIONecN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HEadCafQcH99QcitezEp8A
@coderabbitai

coderabbitai Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e9265320-431a-4da6-85f7-a7236be9d330
📥 Commits

Reviewing files that changed from the base of the PR and between d45750e and d7b23fc.

📒 Files selected for processing (1)
  • docs/tutorials/generic_ioc.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The Generic IOC tutorial adds a date-based release-tag convention for cases without a clear primary support module. It gives 2026.9.1 as the tag for the first release of September 2026.

Changes

Generic IOC release tags

Layer / File(s) Summary
Date-based release-tag guidance
docs/tutorials/generic_ioc.md
The tutorial adds 2026.9.1 as an example tag for the first September 2026 release when a Generic IOC has no clear primary support module.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to d7b23

No actionable merge-blocking issue is established in this documentation change.

Architecture Summary

Architecture risk: 🔵 Low · up to d7b23

The change affects 1 system.

Changed systems: docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — docs (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in docs/tutorials/generic_ioc.md: Adds a date-based release-tag convention for Generic IOCs without a clear primary support module, with 2026.9.1 as the first September 2026 release.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: documenting date-based tags for generic IOCs.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@gilesknap
gilesknap merged commit ae98a0b into main Oct 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant