TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

Internal Packages for Bitbucket

13 posts · Aug 2024 – Jul 2026

What this trail covers

Bitbucket Cloud offers a native container registry integrated with Bitbucket Cloud workflows, allowing teams to publish, manage, and consume container images. It supports repository permissions, API token access control, and will transition to consumption-based billing. Recent enhancements include image and tag deletion, automated garbage collection for storage optimization, and preparation for general availability with a consumption-based pricing model for storage and network traffic. The new Bitbucket Packages feature will provide a central place to publish, manage, and consume artifacts, starting with container images, and will expand to cover additional languages and ecosystems.

All Atlassian trails
  1. Share packages across your workspace with internal packagesIntroduced 'internal packages' for Bitbucket Packages, allowing repository admins to grant read access to a package across all repositories in a workspace without granting access to the source code repository. This addresses friction points like repetitive access requests, oversharing of source code, and stalled pipelines. Internal packages only change read access, not write access, and the source repository remains hidden from users without direct repository access.
  2. Bitbucket Packages adds PyPI and NuGet supportThis post announces the addition of PyPI and NuGet registry support to Bitbucket Packages. It details how this extends the existing unified package management system, which previously supported container registries, Maven, and npm. Key technical aspects include: unified permissions (repository-level Admin, Write, Read apply to packages), reduced context switching by publishing/pulling from the same platform as code, and unified billing drawing from shared storage and network allowances. It also outlines the setup process for Python and .NET tools, including authentication via Atlassian API tokens and the use of BITBUCKET_PACKAGES_USERNAME and BITBUCKET_PACKAGES_TOKEN variables in Bitbucket Pipelines. The post also touches on pricing tiers (Standard and Premium) and storage/network overage costs.
  3. Trace packages back to their source pipelineThis post introduces the 'Source Pipeline' feature for Bitbucket Packages, which links published artifacts directly to the pipeline run that created them. This provides enhanced traceability, faster investigation, and greater confidence in releases by making the origin of a package artifact visible directly from the artifact view. The feature is enabled by default for packages published using the Bitbucket Pipelines integration and requires no new release process.
  4. Introducing Package triggers in Bitbucket PipelinesIntroduces a new `package-artifact-created` trigger for Bitbucket Pipelines. This trigger allows custom pipelines to be automatically executed when a package artifact is created in Bitbucket Packages. It provides package-specific variables for conditions and scripts, enabling targeted automation for validation, scanning, promotion, and notification workflows. The post details the configuration, available variables, and considerations for preventing infinite loops.
  5. Prevent container image overwrites with immutable tags in Bitbucket PackagesIntroduces immutable tags for the Bitbucket Packages container registry. This feature allows workspace admins to configure container image tags to be protected from being overwritten, moved, or modified after their initial push. Options include protecting no tags, all tags, or specific tags based on custom RE2 regular expression rules. This enhances reproducibility, reduces deployment risk, and supports compliance requirements.
  7. Bitbucket Packages now supports Maven and npmThis post expands the Bitbucket Packages feature to include support for Maven and npm packages, in addition to the previously launched container registry. It addresses the fragmentation of package management by unifying Maven and npm artifacts within the Bitbucket platform, thereby eliminating duplicated permissions, broken workflows, and unnecessary costs. Key features include the ability to publish and install Maven and npm packages using existing tools, unified permissions automatically applied based on repository access, and full visibility into packages and their versions. The post also details the cost structure, which is bundled into the existing Packages feature with shared storage and network limits across all package types. Getting started involves connecting the Bitbucket workspace to an Atlassian organization and being on a paid monthly plan. Future plans include support for PyPI and NuGet, immutable tags, and per-type usage breakdowns.
  8. Authenticate Bitbucket Packages with native Pipelines authenticationIntroduces native authentication for Bitbucket Packages container registry using Bitbucket Pipelines' built-in `BITBUCKET_PACKAGES_USERNAME` and `BITBUCKET_PACKAGES_TOKEN` environment variables. This eliminates the need for manual token generation, storage, and rotation, enhancing security with short-lived, per-pipeline-step tokens. Provides examples for direct `docker login` and using the `atlassian/bbc-packages-push-container-image` pipe.
  9. Simplify container management with Bitbucket Packages (now GA)This post announces the General Availability (GA) of Bitbucket Packages, a native container registry within Bitbucket Cloud. It details the transition to a paid pricing model, including storage and network traffic costs for Standard and Premium plans. The post highlights benefits such as reduced context switching, lower costs, simplified administration through repository-level permissions, and the ability to push/pull using Docker CLI with API tokens. It also outlines upcoming features like immutable tags and enhanced Pipelines integration, and mentions the expansion to support language packages.
  10. [Open beta] Container image and tag deletion now available in Bitbucket PackagesIntroduces container image and tag deletion capabilities for Bitbucket Packages, enabling users to remove outdated or unused images and tags. Implements automated background garbage collection to reclaim storage space by deleting unreferenced blobs. Details the process for deleting individual tags and entire container images, including required permissions. Prepares for the upcoming general availability release (December 3, 2025) by outlining the consumption-based billing model for storage and network traffic, including overage charges.
  11. [Open beta] Introducing Packages: native container registry in Bitbucket CloudThis post announces the open beta of Bitbucket Packages, a native container registry for Bitbucket Cloud. It details the core functionality of publishing and consuming container images, the rationale behind its development (addressing fragmented workflows, permission inconsistencies, and inefficiencies), and the beta release details. It also outlines the pricing model for the general availability launch (storage and network traffic overages) and provides instructions on how to get started, including creating package records, authenticating with API tokens, building and pushing images, and viewing published images. Future enhancements planned include deletion and garbage collection, enhanced Pipelines integration, and support for additional package types.
  12. Bitbucket Packages is coming soon: one important step you need to takeThis post announces the upcoming launch of Bitbucket Packages, which will include a built-in container registry for Docker images. It highlights the benefits of a unified platform for code, pipelines, and artifacts, addressing pain points of context switching, separate permission management, and multiple vendors. The feature will offer workspace-level namespaces, repository-linked images inheriting permissions, and a unified developer experience. It will be consumption-based with base limits included in Standard and Premium plans. A prerequisite for access is linking Bitbucket workspaces to Atlassian organizations to enable the new billing experience. Future expansion to other package types is planned.
  13. Migrating Your AWS CodeCommit Repository to Bitbucket CloudThis post details a step-by-step guide for migrating AWS CodeCommit repositories to Bitbucket Cloud, including cloning, creating a new repository, adding remotes, pushing code, and migrating pull requests using a Python script and Bitbucket Cloud APIs. It also covers verification and updating remote URLs.