Skip to content
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.

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

Adopt upcoming Swift Evolution metadata file changes #2

Closed
dempseyatgithub opened this issue Mar 19, 2024 · 5 comments · Fixed by #4
Closed

Adopt upcoming Swift Evolution metadata file changes #2

dempseyatgithub opened this issue Mar 19, 2024 · 5 comments · Fixed by #4
Assignees

Comments

@dempseyatgithub
Copy link

Hi, I'm James Dempsey, a member of the Swift Website Workgroup.

As part of the workgroup one area I’ve been focused on is the Swift Evolution Dashboard and the JSON file of evolution proposal metadata available at https://download.swift.org/swift-evolution/proposals.json.

I’m filing this issue because a GitHub search shows that this project references that URL.

I wanted to let you know that we are in the process of making some proposed changes to the schema and naming of the metadata file.

The proposed modifications are in the Swift Forums post at https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.

Please feel free to provide any feedback in that thread.

That post also describes the transition plan to migrate to the new metadata schema.

During the transition period, the proposal.json file will continue to be available at its current URL with its current schema.

A file with the new schema will also be available during the transition period.

For full details and to provide any feedback you may have, please review the post in the Swift forums.

@ole
Copy link
Collaborator

ole commented Mar 19, 2024

@dempseyatgithub Thanks a lot for the heads-up, James, that's very kind!

I plan to update the Alfred workflow to be compatible with the new format in a timely manner once the transition period starts.

@dempseyatgithub
Copy link
Author

You're very welcome @ole. There's no need to break things unnecessarily, so it seemed like the best approach.

I saw your feedback in the forums. I'm out and about at the moment, but will reply later.

@dempseyatgithub
Copy link
Author

An update that review period for the updated Swift Evolution metadata schema has ended.

The transition period to migrate to the new metadata schema and file has begun and will run through July 22, 2024.

Full details of the transition are available here:
https://forums.swift.org/t/swift-evolution-metadata-transition/71387

@ole ole self-assigned this May 14, 2024
ole added a commit that referenced this issue May 14, 2024
This change adapts to schema version 1.0.0 of the Swift Evolution metadata file format, which went live on 2024-04-21 (with schema version "0.1.0" during the transition). For more info on the changes in the new schema, see James Dempsey’s posts at https://forums.swift.org/t/swift-evolution-metadata-transition/71387 and https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.

The old schema will stop working on 2024-07-22, so we need to ship an update before then.

Fixes #2.
@ole
Copy link
Collaborator

ole commented May 14, 2024

This is now in progress: #4

@ole ole closed this as completed in #4 May 21, 2024
ole added a commit that referenced this issue May 21, 2024
This change adapts to schema version 1.0.0 of the Swift Evolution metadata file format, which went live on 2024-04-21 (with schema version "0.1.0" during the transition). For more info on the changes in the new schema, see James Dempsey’s posts at https://forums.swift.org/t/swift-evolution-metadata-transition/71387 and https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.

The old schema will stop working on 2024-07-22, so we need to ship an update before then.

Fixes #2.
@ole
Copy link
Collaborator

ole commented Jul 22, 2024

This is now live in v2.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants