Skip to content

E-26: Deprecation policy, @deprecated workflow, and automated UPGRADE guides #97

Description

@hakeemRash

Value: There is no deprecation mechanism, and auto-release.yml already derives releases from CHANGELOG.md. Add a Deprecations::trigger() helper (emits E_USER_DEPRECATED, routed through the new LogPort) plus a CI step that generates UPGRADE-x.y.md from the CHANGELOG Changed/Removed sections — which the existing hkm upgrade command can surface.

Where: new helper, tools/src/commands/upgrade.zig, CI.

Effort: M · Impact: Med

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort:MMedium effortenhancementNew capability or ergonomic upgradeimpact:medMedium impactreleaseRelease engineering & versioning

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions