Skip to content

[Spec] Auto generate manifests for newer versions #236105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
+87 −0
Open

[Spec] Auto generate manifests for newer versions #236105

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
5eeeafd
[Spec] Auto generate manifests for newer versions
vedantmgoyal9 Mar 9, 2025
0a4010b
Fix file extension
vedantmgoyal9 Mar 20, 2025
659f8ea
Merge branch 'master' into patch-1
vedantmgoyal9 Mar 20, 2025
d8cf23d
Merge branch 'microsoft:master' into patch-1
ItzLevvie Mar 24, 2025
8fce930
Merge branch 'microsoft:master' into patch-1
ItzLevvie May 2, 2025
bfa2144
Merge branch 'microsoft:master' into patch-1
ItzLevvie May 4, 2025
3032996
Merge branch 'microsoft:master' into patch-1
ItzLevvie May 9, 2025
32c8192
Merge branch 'microsoft:master' into patch-1
ItzLevvie May 15, 2025
01ef8d8
Merge branch 'master' into patch-1
vedantmgoyal9 Jun 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Loading
Loading status checks…
Fix file extension
@vedantmgoyal9
vedantmgoyal9 authored Mar 20, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode
commit 0a4010bd60751862cd32f76e81f44eb9cf72a96c
2 changes: 1 addition & 1 deletion doc/specs/#500 - Auto generate manifests for newer versions.md
View file
Original file line number Diff line number Diff line change
@@ -47,7 +47,7 @@ The proposed automation will automatically open pull requests (PRs) for new vers
}
```

The above JSON defines automation metadata and will be stored in a `.auto_updates.yaml` file alongside `.validation` files.
The above JSON defines automation metadata and will be stored in a `.auto_updates.json` file alongside `.validation` files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would probably be better to have a separate directory structure specifically for auto-updates instead of including metadata in the manifests folder. While having the data right next to all of the manifests makes it easy for users to find, it greatly increases the complexity cost of a solution since whatever is built will have to recursively filter through all the directories to find the metadata files instead of filtering to only a known sub-tree


### Automation Workflow