Show Woodpecker version on pipeline details

[Sim-hu]

Stores the server version at pipeline creation time so that historical pipelines show the version they were actually run on, rather than the current server version.

Changes:

• Add version field to the Pipeline model (xorm auto-syncs the new column)
• Set version in both Create() and Restart() pipeline flows
• Display the version in the debug Tab
• Add TypeScript type and i18n string

Closes #4204

[woodpecker-bot]

Account with automation patterns detected 🤖

@Sim-hu

We analyzed recent public events and found several patterns that are frequently associated with automated scripts or AI agents.

Human? 49% likely to be a human.

Signal	Points	Detail
Many recent forks	+51	10 repos forked within 24 hours

Have thoughts about this account? Let the community know.

_{🕵🏽 Analyzed 189 public events via AgentScan}

[qwerty287]

Please run make generate-openapi: https://ci.woodpecker-ci.org/repos/3780/pipeline/32731/32

[qwerty287]

@Sim-hu could you post a screenshot of this new feature?

[Sim-hu]

[qwerty287]

Thanks. Please move that info to the debug tab.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 33.31%. Comparing base (26a01ec) to head (33265d5).
⚠️ Report is 14 commits behind head on main.

Files with missing lines	Patch %	Lines
server/pipeline/create.go	0.00%	1 Missing ⚠️
server/pipeline/restart.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6316      +/-   ##
==========================================
- Coverage   33.32%   33.31%   -0.01%     
==========================================
  Files         420      420              
  Lines       28333    28335       +2     
==========================================
  Hits         9441     9441              
- Misses      18014    18016       +2     
  Partials      878      878              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[qwerty287]

Thanks, wouldn't put it into it's own Panel. We usually only have one panel.

With a proper header ("Woodpecker version") and then just the version without translated string below is what I'd do.

[6543]

old pipelines:

new pipelines:

PS: screenshot updates are always welcome on UI changes ;)

[qwerty287]

It now looks like this.

Some more padding to the top would be good.

And not sure, but do others think the size is fine? Because in my opinion the text is a bit too small.

What do you think about something like this? With a code block.

Corresponding code would be

      <InputField v-if="pipeline.version" :label="$t('repo.pipeline.version_header')" class="pt-4">
        <p class="text-wp-text-alt-100 mb-2 text-sm">{{ $t('repo.pipeline.version') }}</p>
        <pre class="code-box">{{ pipeline.version }}</pre>
      </InputField>

and you have to change the translation string.

[6543]

[6543]

thanks 🚀