Add AI meeting summaries

notes/2026/summary-2026-06-04.md

@@ -0,0 +1,40 @@
+# Meeting Summary for Working Group Meeting
+
+**NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated
+content may be inaccurate or misleading. Always check for accuracy. If in
+doubt, please consult the meeting recording at
+https://youtube.com/@GraphQLFoundation/playlists
+
+- Meeting start: 2026-06-04T17:26:02Z
+- Meeting end: 2026-06-04T18:05:25Z
+- Summary start: 2026-06-04T17:26:02Z
+- Summary end: 2026-06-04T18:04:50Z
+
+The GraphQL specification team held a meeting to discuss two main agenda items: directives on directives and the upcoming GraphQL JS v17 release. Benoit presented the directives on directives feature, which is currently at RFC2 stage and waiting for more approvals, with a minor discussion about whether to include the deprecated argument in the introspection field. The team agreed to keep the argument consistent with existing implementations rather than introducing a new pattern. Yaacov led the discussion on the GraphQL JS v17 update, announcing the planned release date of June 15th after years of development work by the team. The new version includes breaking changes, cleaning up the codebase, and introduces incremental delivery features under an experimental flag. The team discussed the need to create a highlight reel of new features and announced upgrade guides for users still on older versions. Matt raised a question about creating a GAPS (Gaps and Ambiguities) working group to document known specification gaps and provide guidance to implementers on best practices.
+
+## Next Steps
+
+- Yaacov: Work on a "highlight reel" summary of the top new features and changes in GraphQL JS v17 for the main GraphQL blog and broader announcement channels.
+- All attendees: Review and provide feedback on the GraphQL JS v17 upgrade guide and release notes, especially focusing on clarity and necessary details for users upgrading from older versions.
+- Michael: Pull out the lookup specification from composite schemas and propose it as a gap/specification issue for further documentation and discussion.
+- Matt: Document and enumerate known gaps/specs (including lookup and identity approaches) under the Golden Path Working Group, inviting others to contribute documentation and recommendations.
+- Rob: Add an agenda item to the next secondary meeting to request reviews on spec work, and coordinate with others to ensure reviews are completed before the next spec freeze.
+- All attendees: Help spread the word about the upcoming GraphQL JS v17 release and encourage implementers and users to review and prepare for the update.
+
+## Summary
+
+### Directives and Spec Release Planning
+
+The meeting began with Lee noting that Benjie's agenda items were moved to the next meeting due to his absence. Lee introduced the topic of directives on directives, which Benoit was assigned to discuss. The group was reminded that there are two months until the next spec release freeze, encouraging participants to focus on finalizing late-stage items before the next meeting.
+
+### Directives PR Discussion and Approval
+
+The team discussed a PR for directives on directives which is currently at RFC2 stage. Benoit presented the proposal and addressed a question raised by Benjie about whether to include the deprecated argument on the directives introspection field. The team debated consistency with existing implementations and decided to keep the argument as proposed. They also discussed the ability to extend directives with new directives, though there was some uncertainty about adding new arguments to existing directives. The team agreed to advance the proposal to accepted status and Lee merged it into the draft spec.
+
+### GraphQL JS Version 17 Release
+
+Yaacov announced the upcoming release of GraphQL JS version 17.0 on June 15th, highlighting breaking changes and new features including incremental delivery with a cylinder flag. The team discussed creating a highlight reel of new features to promote the release and reviewed the newly updated GraphQLJS.org documentation, particularly praising the upgrade guides. Rob mentioned he would have an agenda item in the secondary meeting for reviews to help get the release over the line in two months.
+
+### GAP Working Group Discussion
+
+Matt proposed creating a GAP working group to document known gaps and specifications that need to be addressed, particularly focusing on identity-related specifications. Michael and Matt discussed potentially pulling out the lookup specification from composite schemas as a separate gap item. The group determined that this initiative might fit better under the existing Golden Path Working Group rather than as a separate entity, with Michael agreeing to propose the lookup specification as a gap for further discussion.