thx!!

I wonder how we are going to port the existing changelog since we symlink the main changelog in our packages and I don't necessarily want to remove the existing graphql changelog

Yeah, I've wondered the same. Maybe keep it as CHANGELOG_OLD.md and then just link once from the shared one to it?

E.g. add the following to the new changelog:

### version xxx

- Transfer ownership to Sentry. To see the old changelog from previous versions go to [here](link/to/old/changelog.md)

or something like that.

thx, will get to this PR once the next sentry flutter release is out

@buenaflor Are there any updates?

@buenaflor or @vaind any chances of moving forward with this? :D By download count if would be on the 6th place of all Sentry packages in the Dart ecosystem

can we change the folder namesentry_link -> link? to keep in line with the other namings

Sure

craft.yml still needs an entry link for the pub dev section

I'll take a look at it.

Maybe we can also setup a simple CI for running the tests similar to hive.yml

nvm we can do this after the pr

@kahest do we need to look out for anything specific when transferring external repos to ours?

So far we:

• changed license to MIT
• old changelog is internally part of sentry_link for visibility
• new changes will just be part of the main changelog as usual

Handing over the package name on pub.dev still needs to be coordinated too.

for my understanding: since we'll use the same pubspec config, any new release will just update the sentry_link package directly right?

for my understanding: since we'll use the same pubspec config, any new release will just update the sentry_link package directly right?

Yeah, but I need to hand over the ownership of the "name" on pub.dev. Otherwise the upload will just fail

what about this

• we can merge this as is
• I'll set up CI and check if everything is running fine
• check code more in depth etc...
  • just a sanity check
• then when everything is clear we can do all the steps for uploading, e.g adding a target to craft, transfer ownership etc...

wdyt?

Sounds good. I'm happy to jump on call or something for the package transfer on pub. I guess that's easier than sending messages back and forth

Hey, @buenaflor what's the status of merging this?

Regarding this point

Rename the folder from sentry_link to just link or graphql

any specific reason it's called sentry_link in general? I'm thinking about renaming it to graphql to be a bit more specific but not sure 🤔

The name comes from link which is the term from gql (the GraphQL Dart library) for something that sends the GraphQL queries. The term is also used by the Apollo ecosystem in the JavaScript world. So I would assume it's somewhat clear what it means to people using GraphQL.

Renaming the folder is fine, but it's unfortunately not possible on pub.dev

@ueman gotcha, let's leave it then at link

I'll do a quick check then merge this later