Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add metadata/patch stripping to matrix version tag renderings

Open
#522 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
build-system

Research direction

Start by tracing the matrix version tag rendering and how dependency names are passed into compound version names. Compare the existing stripMetadata template behavior for regular image versions with matrix versions, then evaluate the three approaches listed in the issue. Done means matrix tags strip patches or metadata cleanly while preserving the intended component versions.

Written by the indexing model from the issue text.

Description

cvp:1 docker tdp:1

I think we should specify the example without the build number.

    version: "2026.05.1"

Originally posted by @bschwedler in https://github.com/posit-dev/images-workbench/pull/94#discussion_r3226900436


Regular image versions can use the {{ Version |stripMetadata }} template pattern to create a tag with the version metadata stripped off. Since matrix versions typically have compound version names (ex. R4.6.0-python3.13.13), we cannot apply the same template pattern to them and expect a clean result.

To implement this functionality, we would need to alter at least one of:

  • How dependency names are passed into the compounded version name
  • Use regex to trim patches/metadata off of versions in a compounded string
  • Fundamentally change tag pattern structure for matrix versions so we could use a pattern like {{ '-' | join(component_versions | stripMetadata) }}
Dominant language
Python
Stars
2
Forks
0
Avg merge
2d 23h
Merged PRs (30d)
20

Getting set up

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 posit-dev/images-shared

All issues in posit-dev/images-shared

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.