In the Event.exception constructor, modify a clone of the args argument instead of args itself

[andrewkolos]

Hotfix for #1195 for package:unified_analytics v6. This is somewhat necessary because the current flutter beta depends on v6.

Note that merging this PR as-is won't result in a publish. This PR exists for the sake of code review.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[andrewkolos]

@devoncarew

Do you know if updating

tools/.github/workflows/publish.yaml

Lines 1 to 9 in e83caee

	# A CI configuration to auto-publish pub packages.
	name: Publish
	on:
	pull_request:
	branches: [ main ]
	push:
	tags: [ '[A-z]+-v[0-9]+.[0-9]+.[0-9]+' ]

to run against any branch would work for publishing patches to older versions of packages? Assuming that would work, do we want it to (are there branch protections that we have on main that we would then want on all branches)? I'm happy to track this in a separate issue if we don't want to solve it today.

[andrewkolos]

Note for @kenzieschmoll: you can ignore the .github/workflows config file changes. This was cherry-picked from main just to get this branch tested on CI.

[devoncarew]

Hi!

Do you know if updating to run against any branch would work for publishing patches to older versions of packages? Assuming that would work, do we want it to (are there branch protections that we have on main that we would then want on all branches)? I'm happy to track this in a separate issue if we don't want to solve it today.

I think we want to:

• create a branch from the tag of unified_analytics that we want to patch (https://github.com/dart-lang/tools/tags)
• apply the changes, push it up in a PR for review for merge into that branch
• not try to use the publishing automation to publish that new patch, but publish locally from disk

Our publishing automation isn't really set up to handle publishing older patches; that's a rare enough occurrence that I think it's reasonable to handle it by manually publishing from a branch from disk.

[andrewkolos]

SGTM. The first step is already satisfied here, so I will publish this myself once this gets an approval.