Request
Could AltMount publish a supported maintenance branch or tag based on 0b202e0 that contains the merged ARR webhook URL redaction fix from #837 (ad3a98e) and its focused tests?
Context
The current main line now includes the V3 shared metadata/store work and later migrations. For deployments that remain on pre-V3 storage, moving directly from 0b202e0 to main crosses metadata/store and migration boundaries rather than being a focused security update. A supported upstream-owned 0b-line backport would let users receive the logging fix without adopting the V3 migration path prematurely.
This does not request a change to main; an upstream-maintained branch/tag with documented support and upgrade semantics is sufficient. If this is not a supported maintenance direction, please advise the recommended upgrade path for pre-V3 stores.
Request
Could AltMount publish a supported maintenance branch or tag based on
0b202e0that contains the merged ARR webhook URL redaction fix from #837 (ad3a98e) and its focused tests?Context
The current
mainline now includes the V3 shared metadata/store work and later migrations. For deployments that remain on pre-V3 storage, moving directly from0b202e0tomaincrosses metadata/store and migration boundaries rather than being a focused security update. A supported upstream-owned 0b-line backport would let users receive the logging fix without adopting the V3 migration path prematurely.This does not request a change to
main; an upstream-maintained branch/tag with documented support and upgrade semantics is sufficient. If this is not a supported maintenance direction, please advise the recommended upgrade path for pre-V3 stores.