Skip to content

merging develop into main for release v0.9.0#339

Merged
boegel merged 162 commits into
mainfrom
develop
Aug 22, 2025
Merged

merging develop into main for release v0.9.0#339
boegel merged 162 commits into
mainfrom
develop

Conversation

@trz42
Copy link
Copy Markdown
Contributor

@trz42 trz42 commented Aug 22, 2025

SSIA

boegel and others added 30 commits February 6, 2025 14:54
…king it required

Co-authored-by: Thomas Röblitz <trz42@users.noreply.github.com>
Co-authored-by: Thomas Röblitz <trz42@users.noreply.github.com>
…app.cfg.example

Co-authored-by: Thomas Röblitz <trz42@users.noreply.github.com>
…e keys don't have meaning, and all meaning is in the values
git diff from merge-base instead of from HEAD
Caspar van Leeuwen and others added 27 commits August 19, 2025 17:50
…ned. Also, log the general args to the log
…composing the table with only the last builds. Finally, add resorting for an output that is sorted alphabetically by 'for' architecture
…holder and allow processing jobs that require different placeholder values
don't replace self.scontrol_command in process_new_job
Add option to bot:status to print the status only for the last build
replacing more `arch_target_map` with `node_type_map` in README.md
Co-authored-by: Kenneth Hoste <kenneth.hoste@ugent.be>
…n bot configuration by new_job_instance_repo/build_on_arch/build_for_arch/jobdir
also mention v0.9.0 release notes that `initial_comment` was replaced in bot configuration by `new_job_instance_repo`/`build_on_arch`/`build_for_arch`/`jobdir`
update action versions in scorecards CI

- name: Install markdownlint-cli
run: npm install -g markdownlint-cli

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 7: npmCommand not pinned by hash
Click Remediation section below to solve this issue
@@ -0,0 +1,7 @@
ARG smee_client_version=4.2.1

FROM node:lts-alpine

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 7: containerImage not pinned by hash
Remediation tip: pin your Docker image by updating node to node@sha256:d2b6b5aedb5b729f68ee1129e0f5a5d4713d93f82448249e82241876d8e8d86e
Click Remediation section below for further remediation help

FROM node:lts-alpine
ARG smee_client_version
RUN npm install --global smee-client@${smee_client_version}

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 7: npmCommand not pinned by hash
Click Remediation section below to solve this issue
@boegel
Copy link
Copy Markdown
Contributor

boegel commented Aug 22, 2025

Let's follow up on the pinned-dependencies check failure via:

@boegel boegel merged commit a552da9 into main Aug 22, 2025
12 of 13 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.

9 participants