---
schema_version: "1"
id: 4b075cc6fa94e512e742676e1b1973fa7d2d73b85ad11025bcd3ec5d1fdca824
title: Update Your First-Generation Managed Package
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/first-generation/packaging-upgrading.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg1-dev/guide/packaging-upgrading.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 1fedca9cb58d8244ce54dd6515703c31942005adfab41f5844ef86172f6e062f
products:
  - First-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Update Your First-Generation Managed Package

Your app is ready for an update. Learn how to fix small issues with patches and make major changes with upgrades.

- **[Package Versions in First-Generation Managed Packages](https://developer.salesforce.com/docs/platform/pkg1-dev/guide/dev-package-versions-overview.md)**


    A package version is a number that identifies the set of components uploaded in a package. The version number has the format _majorNumber.minorNumber.patchNumber_ (for example, 2.1.3).

- **[Create and Upload Patches in First-Generation Managed Packages](https://developer.salesforce.com/docs/platform/pkg1-dev/guide/patches-creating.md)**


    Patch versions are developed and maintained in a patch development org.

- **[Work with Patch Versions](https://developer.salesforce.com/docs/platform/pkg1-dev/guide/packaging-patches-about.md)**


    A patch version enables a developer to change the functionality of existing components in a managed package. Subscribers experience no visible changes to the package. Patches are minor upgrades to a Managed - Released package and only used for fixing bugs or other errors.

- **[Versioning Apex Code](https://developer.salesforce.com/docs/platform/pkg1-dev/guide/packaging-behavior-apex.md)**


    When subscribers install multiple versions of your package and write code that references Apex classes or triggers in your package, they must specify the version that they’re referencing.

- **[Apex Deprecation Effects for Subscribers](https://developer.salesforce.com/docs/platform/pkg1-dev/guide/packaging-effects-subscribers.md)**


    Explore how deprecation of an Apex method impacts subscribers that install your managed package.