{"version":"2.1.229","anchor":"the-published-code-change-event-no-longer-assumes-a-pull-req","canonical_anchor":"the-published-code-change-event-no-longer-assumes-a-pull-req","heading":"The published code change event no longer assumes a pull request","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/the-published-code-change-event-no-longer-assumes-a-pull-req","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### The published code change event no longer assumes a pull request\n\nThe event for work sent out for review no longer assumes GitHub pull requests.\n\n**What**\n\nThe SDK event that fires when work from a session goes out for review is now described in provider-neutral terms, with the provider field documented as carrying other values for other review systems and the URL as the published change rather than a PR link.\n\n**Evidence**\n\n`other values for other review systems in internal builds`\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}