> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/administration/updates/options/update-republishing-options.md).
# Update Republishing Options
*Applies to: Patch My PC Publisher V2.x*
## Overview
The **Update Republishing Options** section controls how republished third party updates are named. Republishing is required when an existing update needs to be replaced due to changes in content or metadata.
Common scenarios that require republishing include updates where customizations were added or modified, detection logic was corrected, or the update needs to be signed with a new code signing certificate. In general, any change that affects the update CAB file or its digital signature requires the update to be republished.
{% hint style="success" %}
**Tip**
For more information on Republishing, see [Customizations](/patch-my-pc-publisher/customizations-right-click-options.md).
{% endhint %}
By default, when an update is republished, the Publisher appends a timestamp to the update name indicating when the republish occurred. This makes it clear in the ConfigMgr console that the update is a republished revision and shows the exact date and time of the republish. The example shown in the image above demonstrates how a republished Google Chrome update would appear with this appended information.
If the option **Do not append republished updates with a republished datetime** is selected, the republished update keeps the original update name and no timestamp is added. The update is still republished and supersedes the previous revision (if that option was selected during republishing), but there is no visible indication in the name that a republish occurred.
{% hint style="info" %}
**Note**
Republishing only applies to an existing update version. When an update is republished, the Publisher republishes the same version and creates a new revision of that update with a new Update ID.
If an administrator attempts to republish an update and the specified version is not found, the Publisher does not republish. Instead, a standard publish occurs for the newer version, and it is treated as a new update rather than a republished revision.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.patchmypc.com/patch-my-pc-publisher/administration/updates/options/update-republishing-options.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.