Latest Changes

GitHub App

Latest Changes

GitHub App

Latest Changes

A GitHub App that updates release notes when a pull request is merged into a repository's default branch.

It looks for the first existing file in this order:

  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md

If none of these files exists, the app creates release-notes.md.

An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.

Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:

LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal

Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.

For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:

Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure

You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.

Automatic labels

Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.

auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock

The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.

Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.

Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.

Install

You can install the GitHub App.

It needs the following permissions:

PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)

The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.

Self Host

If you prefer, you can self host it.

Deploy

You can deploy it to FastAPI Cloud:

uv run fastapi deploy

Create a GitHub App

Create a new GitHub App.

Enable webhooks, and set the URL to your app:

https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:

uv run python -c "import secrets; print(secrets.token_urlsafe())"

Save it in the webhooks secret field.

Subscribe to the Pull request event and configure the repository permissions listed above.

After creating the app, generate and download a private key.

Configure these values in your FastAPI Cloud dashboard:

NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret

Install

You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.

License

This project is licensed under the terms of the MIT license.

Developer

Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Latest Changes
GitHub App
Latest Changes
GitHub App
Latest Changes
A GitHub App that updates release notes when a pull request is merged into a repository's default branch.
It looks for the first existing file in this order:
  1. release-notes.md
  2. docs/release-notes.md
  3. docs/en/docs/release-notes.md
  4. CHANGELOG.md
If none of these files exists, the app creates release-notes.md.
An existing file must contain ## Latest Changes. That section may contain only the ### sections listed below, with each section appearing at most once.
Each pull request must have exactly one Latest Changes label: either one of the section labels below or release. A section label determines the section:
LabelSection
breakingBreaking Changes
securitySecurity Fixes
featureFeatures
bugFixes
refactorRefactors
upgradeUpgrades
docsDocs
lang-allTranslations
infraInfrastructure
internalInternal
Pull requests with the release label are skipped. The release label is mutually exclusive with the section labels above.
For pull requests targeting the default branch, the app reports a commit status named latest-changes/label:
Matching labelsStatus
NonePending
One section label or releaseSuccess
More than one without automatic-label configurationFailure
You can require this status in a branch rule or ruleset. Configure the Latest Changes GitHub App as the expected source of the status.
Automatic labels
Add .github/latest-changes.yml to enable automatic labeling. Each supported label maps to an ordered list of path rules. A string includes matching paths, while an exclude object excludes a matching path from that label. The first matching rule for one path and label wins.
auto-labels:
docs:
- docs/en/docs/**
- docs_src/**lang-all:
- exclude: docs/*/**/_*.md
- docs/*/docs/**internal:
- .github/**
- scripts/**
- uv.lock
The app selects the highest-priority matching label only when every changed path is classified. An unclassified source or metadata change leaves the pull request pending for a manual label. Renames evaluate both the old and new paths.
Automatic labeling also understands dependency changes in the repository-root pyproject.toml. Changes to project.dependencies or project.optional-dependencies match upgrade, while changes to dependency-groups match internal. Other TOML keys remain unclassified. Use auto-labels: {} to enable only these built-in rules.
Automatic selection runs when a pull request is opened and when new commits are pushed. Replacing a supported label manually selects it without rerunning automatic classification. If multiple supported labels are added together, the highest-priority label wins deterministically. A later push may promote the selection to a higher-priority automatic candidate, but never downgrade it.
Install
You can install the GitHub App.
It needs the following permissions:
PermissionAccess
ContentsRead and write
Pull requestsRead and write
Commit statusesRead and write
MetadataRead (automatically included)
The app commits directly to the repository's default branch. If a ruleset prevents direct writes, add the GitHub App to its bypass list with Always allow.
Self Host
If you prefer, you can self host it.
Deploy
You can deploy it to FastAPI Cloud:
uv run fastapi deploy
Create a GitHub App
Create a new GitHub App.
Enable webhooks, and set the URL to your app:
https://your-app.fastapicloud.dev/webhooks/github

Create a webhook secret, e.g. with:
uv run python -c "import secrets; print(secrets.token_urlsafe())"
Save it in the webhooks secret field.
Subscribe to the Pull request event and configure the repository permissions listed above.
After creating the app, generate and download a private key.
Configure these values in your FastAPI Cloud dashboard:
NameTypeValue
GITHUB_CLIENT_IDEnvironment variableThe Client ID from the GitHub App settings
GITHUB_APP_PRIVATE_KEYSecretThe complete contents of the downloaded private key
GITHUB_WEBHOOK_SECRETSecretThe same generated value configured as the webhook secret
Install
You can go to your GitHub App settings, to the "Install App" section, and install it to your repositories.
License
This project is licensed under the terms of the MIT license.
Developer
Latest Changes is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

Report abuse