Runner 3.0.0 update impact

[ahulist]

As mentioned in atlassian.com/bitbucket-pipelines-runner-upgrade-required:

To maintain stable access to the self-hosted runner functionality, and gain the benefits from these improvements (as well as numerous other security and performance updates), all customers are required to upgrade to version 3.0.0 or above before December 2, 2024.

It does not state here (nor anywhere else I could find), whether existing self-hosted runners below v. 3.0.0 might experience any impact past December 2. Is this date a hard limit and there is some possibility for errors/instability?

[Theodora Boudale]

Hi @ahulist and welcome to the community!

The blog post has been updated with a new section about the impact in case you don't update. I am quoting from the blog post:

What happens if I don’t upgrade?

• Starting December 2nd, any steps running on outdated versions of the Runner will no longer be able to interact with the Pipelines file-storage infrastructure.
• This will mean that steps utilising Artifacts or Caches on these runner versions will no longer function.
• Steps that are not using those features may still function correctly in some situations, but should be assumed to be unstable and no longer supported.

The date of December 2nd is indeed a hard limit.

Please feel free to reach out if you have any questions.

Kind regards,
Theodora

[ahulist]

Thanks for the answer @Theodora Boudale. Just to clarify: does this also apply to self-hosted runners, are they affected in any way? Or just the ones in cloud?

[Theodora Boudale]

Hi @ahulist,

This concerns only self-hosted runners, so, yes, they will be affected. Just to make it clearer, it's about self-hosted runners documented on this page:

• https://support.atlassian.com/bitbucket-cloud/docs/runners/

Cloud runners (for builds running on Atlassian's infrastructure) are maintained by Atlassian. The blog post doesn't apply to Cloud runners.

Kind regards,
Theodora