Release notes

• Oct 2026

  • changed

    Forgejo Runner v13: changes that can break your workflows

    Oct 27, 2026

    We have upgraded the runners of STACKIT Git to Forgejo Runner v13. This release makes expression evaluation stricter, removes legacy workflow commands, limits registry credentials to the job that declares them, and removes the remaining Gitea compatibility. Several cases that used to log a warning now fail the run, so check your workflows for the changes below.

    Invalid expressions and matrices fail the run

    An expression that cannot be evaluated, such as a format() call with fewer arguments than its format string references, now fails the step or job instead of logging a warning. Attempting to exclude a value from a matrix that was never defined in that matrix now causes an error and prevents the workflow from running.

    Check the expressions and matrix definitions in your workflow files.

    Legacy workflow commands are removed

    The ::set-output, ::set-env and ::add-path commands no longer have any effect, and ACTIONS_ALLOW_UNSECURE_COMMANDS does not enable them again. Write to the environment files instead:

    • Replace echo "::set-output name=var::value" with echo "var=value" >> "$FORGEJO_OUTPUT".
    • Replace echo "::set-env name=VAR::value" with echo "VAR=value" >> "$FORGEJO_ENV".
    • Replace echo "::add-path::/custom/bin" with echo "/custom/bin" >> "$FORGEJO_PATH".

    Registry credentials are declared per job

    The runner no longer logs in to registries with the DOCKER_USERNAME and DOCKER_PASSWORD secrets, because these credentials could be sent to a registry they were not meant for. If a job uses an image from a private registry, declare the credentials in that job:

    jobs:
      build:
        container:
          image: private.registry.example/app:latest
          credentials:
            username: ${{ secrets.REGISTRY_USER }}
            password: ${{ secrets.REGISTRY_TOKEN }}

    Gitea compatibility is removed

    The ${{ gitea.* }} context is no longer supported. Replace it with ${{ forgejo.* }} in your workflows.

    Steps no longer run in a terminal

    The runner no longer attaches a terminal to the output of a step. Commands that print colors only when they detect a terminal now print plain text. To get colored output again, set FORCE_COLOR=1. Commands that require a terminal will now fail. For example, replace docker run -it with docker run -i.

    If you operate your own runners

    • Docker Engine 25.0 or later is required. We recommend 28.0.1 or later, because earlier versions can fail to create IPv6 networks with Forgejo Runner v13.
    • The GITEA_DEBUG, GITEA_TRACE, GITEA_RUNNER_CAPACITY, GITEA_RUNNER_FILE, GITEA_RUNNER_ENVIRON and GITEA_RUNNER_ENV_FILE variables are ignored. Remove them from your runner configuration and environment.
    • The container.network_mode option is removed. Use container.network instead.

    For more details, see the release announcement of Forgejo Runner v13.0 and the release notes of Forgejo Runner.

    If you have any questions, feel free to contact our Help Center.

• Sep 2026

  • announcement

    One SSH address for all STACKIT Git instances

    Sep 25, 2026

    On October 27, 2026, from 20:00 to 23:00 (UTC), SSH access to STACKIT Git moves to one shared address. The name of your instance becomes the first element of the repository path. This reduces the publicly exposed surface of your instance and lets us improve the reliability of Git operations over SSH in one place.

    • Previous address: git@ssh.<instance>.git.onstackit.cloud:<owner>/<repository>.git
    • Address after the maintenance: ssh://git@ssh.git.onstackit.cloud/<instance>/<owner>/<repository>.git

    How you are affected

    During the maintenance every Git instance is restarted once and is unavailable for about one minute. The restarts are staggered, so not all instances are affected at the same time. Access over HTTPS, your repositories, your users, your registered SSH keys and your IP allowlists do not change.

    The previous address keeps working until April 27, 2027. Your existing clones and your automation continue to work after the maintenance, so you can move them at your own pace. We remind you before we switch the previous address off.

    What to prepare before October 27, 2026

    • Allow outbound traffic to 213.17.16.145 on port 22, if your network restricts outbound connections.
    • Add the host key of ssh.git.onstackit.cloud, if your systems verify host keys. Its fingerprint is SHA256:I4jgl6ALgx5qOWwpQVC2M613dV7R0Wy6LfQQ5LQKwR4 (ED25519).
    • Make sure the SSH key your client offers to ssh.git.onstackit.cloud is registered in your instance.
    • Identify every place that holds the address: local clones, build pipelines, deployment automation, infrastructure as code module sources and repository mirrors.

    What to do after the maintenance

    Update the remote address of each repository:

    git remote set-url origin "$(git remote get-url origin | sed -E 's#^(ssh://)?git@ssh\.([^.]+)\.git\.onstackit\.cloud[:/]#ssh://git@ssh.git.onstackit.cloud/\2/#')"

    For the full instructions, including how to select the right key when you work with more than one SSH key, see Connect to your repositories with SSH.

    If you have any questions, our Help Center is always at your disposal.

• May 2026

  • announcement

    New Pipeline Approvals & Portal Controls

    May 26, 2026

    We are pleased to announce a major update to STACKIT Git & Pipelines, introducing enhanced security controls, pipeline governance, and advanced identity management features directly from the STACKIT Portal.

    Pipeline Governance: Protected Workflows & Approvers

    To ensure higher resilience and meet enterprise change management standards, we have introduced Pipeline Approvers. Empower your team to ensure the highest quality standards by enabling designated members to review and authorize critical deployment pipelines before execution. There are two ways to implement this functionality depending on your setup:

    • Manual Workflow Approval: A seamless UI-driven configuration within the STACKIT Portal to pause workflows and require manual validation before moving to high-risk deployment stages.
    • Split workflow: Configure your code in two different files, so you get the same final behaviour but with less customization.

    Advanced Identity & Access Management (IAM)

    We have significantly improved user life cycle management and access security:

    • Identity Provider (IdP) Integration: Connect your corporate Identity Provider directly to your STACKIT Git instance to automate user onboarding and federation.
    • Local vs. Technical User Creation: Administrators can now differentiate between standard internal users (Local) and automated automation tokens/accounts (Technical Users), reducing the risk of unauthorized privilege escalation.

    Network & administrative controls from the Portal

    You no longer need to manage advanced configuration with API or backend support requests. The STACKIT Portal now offers full self-service capabilities for:

    • IP Address Whitelisting (ACL Control): Secure your Git repositories by restricting inbound and outbound traffic to trusted enterprise network ranges directly from the instance network settings.
    • User Admin Management: Complete control over user permissions, seat allocations, and project visibility through a unified administrative panel.

• Mar 2026

  • announcement

    STACKIT Pipelines: Introducing STACKIT-managed Runners

    Mar 17, 2026

    We are excited to announce the integration of STACKIT-managed Runners into STACKIT Git, significantly enhancing your Continuous Integration and Continuous Delivery (CI/CD) workflows. This new feature automates and validates your code changes, new features, and critical bug fixes without manual intervention, all within your STACKIT environment.

    Key Highlights:

    • Automated & Scalable CI/CD: STACKIT-managed Runners automatically provision, run, and de-provision based on your code pushes or specific events, ensuring efficient and scalable pipeline run.
    • High GitHub Actions Compatibility: Enjoy approximately 90% compatibility with GitHub Actions, allowing you to leverage existing workflows with minimal adjustments.
    • Secure isolated environments: Every job is running in a completely isolated disk, making sure no leaks to other jobs or instances occur.
    • Broad Development Environment Support: We support popular development environments including Java, Node.js, Salesforce, Go, and Python, with a variety of in-docker images for diverse use cases.
    • Deep STACKIT Ecosystem Integration: Experience seamless and secure integration with other STACKIT services, such as STACKIT Secret Manager. Your code and services remain within the STACKIT Network, enhancing security and speed by avoiding public internet access.
    • Comprehensive Logging & Security: Detailed logs provide insights for pipeline optimization, and sensitive information is automatically obscured for your security.
    • Direct Integration with STACKIT Container Registry: Build and push images directly to the STACKIT Container Registry, streamlining your software development lifecycle within STACKIT.

    This release marks a significant step towards centralizing your entire SDLC within the STACKIT ecosystem.

• Jul 2025

  • announcement

    New STACKIT Git-10 Subscription

    Jul 18, 2025

    From 18 July 2025 we can offer you a new service Git-10 Subscription. This is perfect for small businesses or startups and offers the possibility to provide 10 users with 10 GB of storage at a significantly lower price point.

    Feature: Flexible Storage for STACKIT Git

    As of now, STACKIT Git supports flexible storage. All STACKIT Git instances can now scale their storage capacity as needed, with monthly billing based on actual usage. This provides the flexibility larger organizations require while still allowing smaller teams to scale effortlessly as they grow.

    If you have any questions, our Help Center is always at your disposal.

• Apr 2025

  • announcement

    STACKIT Git is now available

    Apr 1, 2025

    We are happy to announce that you can now request your own dedicated Git instance from the STACKIT portal. This is perfect for teams of up to 100 users.

    With over 130 GB of storage, you will have plenty of space to manage your projects and take control of your software development process.

    STACKIT Git enables teams to collaborate on software development projects while maintaining control and security. Features such as version control, pull requests, issue tracking, and integrated discussions allow you to:

    • Easily track changes and revert to previous versions
    • Work on multiple branches simultaneously
    • Streamline project management and collaboration
    • Improve development cycles and deliver high quality software
    • Keep your code secure in the STACKIT cloud
    • Host your project’s code base in your own fully managed instance, ensuring your data is secure in the STACKIT cloud. Our Git cloud service is designed to meet the needs of teams of all sizes, providing a scalable and reliable solution for software development.

    Find out more about STACKIT Git in our STACKIT Docs.