Merge branch 'SAP:main' into main

Author: TrueBurn

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] "
+type: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Tested with Version**
+v1.x.x
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an new Feature or Improvment
+title: "[FEATURE]"
+type: feature
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/workflows/build.yaml

@@ -21,7 +21,7 @@ defaults:
 jobs:
   build-docker:
     name: Build Docker image
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     permissions:
       contents: read
     outputs:

.github/workflows/publish.yaml

@@ -18,7 +18,7 @@ defaults:
 jobs:
   publish-docker:
     name: Publish Docker image
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     permissions:
       contents: read
       packages: write

.github/workflows/release.yaml

@@ -31,7 +31,7 @@ defaults:
 jobs:
   release:
     name: Trigger release
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     permissions:
       contents: write
 

.github/workflows/stale-issue-pr.yaml

@@ -0,0 +1,52 @@
+name: Stale Issues and PRs
+
+on:
+  schedule:
+    - cron: '45 3 * * *'  # Every day at 2:30 AM UTC
+  workflow_dispatch:  # Manually trigger the workflow through GitHub UI
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    concurrency:
+      group: ${{ github.workflow }}  # Prevent parallel workflows for the same workflow
+      cancel-in-progress: false  # Does not cancel the running workflow, waits for it to finish
+    permissions:
+      contents: write
+      issues: write
+      pull-requests: write
+      actions: write
+
+    steps:
+    - name: Mark stale issues and PRs
+      uses: actions/[email protected]  # Use the latest version of the Stale Action
+      with:
+        # Label to apply to stale issues
+        stale-issue-label: 'stale'
+          
+        # Label to apply to stale pull requests
+        stale-pr-label: 'stale'
+
+        # Number of days before an issue/PR is marked as stale
+        days-before-stale: 180  # If the issue/PR has been inactive for 180 days, it will be marked as stale
+          
+        # Number of days before a stale issue/PR is closed
+        days-before-close: 7  # If the stale issue/PR has been inactive for 7 days day, it will be closed
+
+        # Option to close stale issues and PRs
+        close-issue-label: 'closed'  # Close issues that are marked as stale
+        close-pr-label: 'closed'  # Close PRs that are marked as stale
+
+        # Exclude issues and PRs that have certain labels from being marked stale
+        exempt-issue-labels: 'closed'  # Ignore issues with 'closed' label
+        exempt-pr-labels: 'closed'  # Ignore PRs with 'closed' label
+
+        # Custom message for stale issues
+        stale-issue-message: 'This issue has been marked as stale because it has not had activity for 180 days. It will be closed in 7 days if no further activity occurs.'
+          
+        # Custom message for stale pull requests
+        stale-pr-message: 'This pull request has been marked as stale because it has not had activity for 180 day. It will be closed in 7 days if no further activity occurs.'
+
+        # Remove the stale label when an issue/PR is updated/comments
+        remove-issue-stale-when-updated: true  # Remove the stale label when an issue is updated  
+        remove-pr-stale-when-updated: true  # Remove the stale label when a PR is updated

.reuse/dep5

@@ -22,6 +22,12 @@ Should you wish to work on an issue, please claim it first by commenting on the
 
 If you have questions about one of the issues, please comment on them, and one of the maintainers will clarify.
 
+## Contributing with AI-generated code
+
+As artificial intelligence evolves, AI-generated code is becoming valuable for many software projects, including open-source initiatives. While we recognize the potential benefits of incorporating AI-generated content into our open-source projects there a certain requirements that need to be reflected and adhered to when making contributions.
+
+Please see our [guideline for AI-generated code contributions to SAP Open Source Software Projects](CONTRIBUTING_USING_GENAI.md) for these requirements.
+
 ## Contributing Code or Documentation
 
 You are welcome to contribute code in order to fix a bug or to implement a new feature that is logged as an issue.

CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# Guideline for AI-generated code contributions to SAP Open Source Software Projects
+
+As artificial intelligence evolves, AI-generated code is becoming valuable for many software projects, including open-source initiatives. While we recognize the potential benefits of incorporating AI-generated content into our open-source projects there are certain requirements that need to be reflected and adhered to when making contributions.
+
+When using AI-generated code contributions in OSS Projects, their usage needs to align with Open-Source Software values and legal requirements. We have established these essential guidelines to help contributors navigate the complexities of using AI tools while maintaining compliance with open-source licenses and the broader [Open-Source Definition](https://opensource.org/osd).
+
+AI-generated code or content can be contributed to SAP Open Source Software projects if the following conditions are met:
+
+1. **Compliance with AI Tool Terms and Conditions**: Contributors must ensure that the AI tool's terms and conditions do not impose any restrictions on the tool's output that conflict with the project's open-source license or intellectual property policies. This includes ensuring that the AI-generated content adheres to the [Open-Source Definition](https://opensource.org/osd).
+2. **Filtering Similar Suggestions**: Contributors must use features provided by AI tools to suppress responses that are similar to third-party materials or flag similarities. We only accept contributions from AI tools with such filtering options. If the AI tool flags any similarities, contributors must review and ensure compliance with the licensing terms of such materials before including them in the project.
+3. **Management of Third-Party Materials**: If the AI tool's output includes pre-existing copyrighted materials, including open-source code authored or owned by third parties, contributors must verify that they have the necessary permissions from the original owners. This typically involves ensuring that there is an open-source license or public domain declaration that is compatible with the project's licensing policies. Contributors must also provide appropriate notice and attribution for these third-party materials, along with relevant information about the applicable license terms.
+4. **Employer Policies Compliance**: If AI-generated content is contributed in the context of employment, contributors must also adhere to their employer’s policies. This ensures that all contributions are made with proper authorization and respect for relevant corporate guidelines.

CONTRIBUTING_USING_GENAI.md

@@ -1,4 +1,4 @@
-FROM golang:1.22.5-alpine AS builder
+FROM golang:1.23.5-alpine AS builder
 WORKDIR /src/
 COPY go.mod go.mod
 COPY go.sum go.sum