> This page is for Product Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Accessing Releases

> Stay up to date with the latest NaviPartner releases and updates.

All our release notes are publicly available on GitHub, giving you full transparency into what our development team is working on and what's new.

## GitHub Release Notes

Visit our [<ins>GitHub Releases page</ins>](https://github.com/navipartner/npcore-partners/releases) to access:

* **Latest updates** - See the most recent releases and what's been added or improved
* **Version history** - Browse through all previous releases and their release notes
* **Change logs** - Detailed information about new features, bug fixes, and improvements
* **Development insights** - Understand what our team is actively working on

Simply bookmark the [<ins>releases page</ins>](https://github.com/navipartner/npcore-partners/releases) and check back regularly to stay current with all NaviPartner developments.

## Using releases with GitHub Actions and AL-Go

If you're building a Per-Tenant Extension (PTE) on top of NP Retail and use [<ins>AL-Go for GitHub</ins>](https://github.com/microsoft/AL-Go) for your pipelines, there are three ways to work with NP Retail - reading its source, compiling against it, or pulling a specific release's build output. Two of them need no NaviPartner-specific setup at all.

### Option 1: Reading the AL source

The [<ins>NPCore Partners repository</ins>](https://github.com/navipartner/npcore-partners) itself carries the full AL source, kept current by a daily automated sync from our internal codebase - not the release package described below.

Use this when you need to read or step through NP Retail's source itself - for example, troubleshooting, or using the [<ins>Event Recorder</ins>](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-events-discoverability) to find extension points, the same way you would in Microsoft's base app. It's public, so there's nothing to request access to.

> **Note:** The `.nupkg` file on the [<ins>Releases page</ins>](https://github.com/navipartner/npcore-partners/releases) is the pipeline's packaged build output, not the AL source - for source, browse or clone the repository itself. It's also stable-only, published every Sunday evening; for pre-releases, see the authenticated feed below.

### Option 2: Symbols only

If your pipeline only needs to compile against NP Retail - not read its source - AL-Go can resolve NP Retail's symbols from Microsoft's own AppSource symbols feed, in the standardized `BcNuGet` package format Microsoft is moving Business Central symbol distribution to.

This works out of the box: AL-Go's [<ins>`trustMicrosoftNuGetFeeds`</ins>](https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md#trustMicrosoftNuGetFeeds) setting is `true` by default, and that feed already carries symbols for every AppSource app, NP Retail included. There's nothing to request access to, and nothing to add to your AL-Go settings.

NP Retail is published on the feed as `NaviPartner.NPRetail.symbols.992c2309-cca4-43cb-9e41-911f482ec088`, with each version prefixed by the BC major it was built for - for example `2800.148.0.10000` on BC28, `2700.148.0.10000` on BC27. Don't copy the bare version number straight off the [<ins>Releases page</ins>](https://github.com/navipartner/npcore-partners/releases) into your `app.json`; use the matching `28xx.`/`27xx.`-prefixed version from the symbols feed instead.

Symbols only appear on the feed once that version has finished publishing to AppSource, so the feed can lag a version or two behind the latest weekly GitHub release. If you need the exact latest release the moment it's tagged, use the authenticated feed (Option 3) instead.

Use this for the common case: compiling and testing your PTE against NP Retail's public API surface, without needing the source.

### Option 3: Authenticated access to the main release feed

Both options above cover the weekly stable release. If you need **pre-releases** as well - for example, a warning-only pipeline that compiles against our latest unreleased/insider build to catch upcoming breaking changes early, as recommended in the [<ins>NPCore Partners README</ins>](https://github.com/navipartner/npcore-partners) - you need our main feed: an Azure DevOps Artifacts NuGet feed carrying both releases and pre-releases, which both the GitHub Release Notes and the release `.nupkg` from Option 1 are themselves published from.

This feed requires authentication:

1. Reach out to your NaviPartner point of contact to request access. You'll receive a feed URL and a Personal Access Token (PAT) scoped to read packages.
2. Store the PAT as a secret in your GitHub repository (for example, `NpNuGetFeedToken`).
3. Add the feed to your AL-Go project's [<ins>`trustedNuGetFeeds`</ins>](https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md#trustedNuGetFeeds) setting, in `.github/AL-Go-Settings.json`:

   ```json
   {
     "trustedNuGetFeeds": [
       {
         "url": "<feed URL provided by NaviPartner>",
         "authTokenSecret": "NpNuGetFeedToken"
       }
     ]
   }
   ```

### Which option do I need?

| I need to...                                                   | Use                                                                      |
| -------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Read or step through NP Retail's AL source                     | Reading the AL source (browse the `npcore-partners` repo)                |
| Compile and test my PTE against NP Retail's public API surface | Symbols only (works out of the box, may lag the newest release slightly) |
| Catch breaking changes early, or need a pre-release            | Authenticated access to the main feed                                    |

#### See also

* [<ins>NPCore Partners repository</ins>](https://github.com/navipartner/npcore-partners)