Release the recent changes

[dividedmind]

Let's package up the recent changes.

(BTW, is there a sane and easy way to make it so the plugin version in develop is current? It's still stuck at 0.67.1.)

[jansorg]

@dividedmind The change to the version is only committed to main. If you sync the changes only made to main into develop, then things should be fine.

[jansorg]

If this is just a merge of develop into main without further changes, then this is fine.
I briefly looked at the changes, but did not check all the changes.

[dividedmind]

@dividedmind The change to the version is only committed to main. If you sync the changes only made to main into develop, then things should be fine.

Yeah, but this cumbersome and leads to those ugly back and forth merges. I just wonder if there is a better way.

[jansorg]

@dividedmind The change to the version is only committed to main. If you sync the changes only made to main into develop, then things should be fine.

Yeah, but this cumbersome and leads to those ugly back and forth merges. I just wonder if there is a better way.

Well, we could drop develop and always merge into main. I don't think that we need develop anymore.

[dividedmind]

@dividedmind The change to the version is only committed to main. If you sync the changes only made to main into develop, then things should be fine.

Yeah, but this cumbersome and leads to those ugly back and forth merges. I just wonder if there is a better way.

Well, we could drop develop and always merge into main. I don't think that we need develop anymore.

Yeah, maybe that's a good idea. It might lead to a bit of a version churn, but I think that's okay. appmap-js has more churn and it releases directly — even to external repositories, unlike here where the marketplace releases are manual.

@hleb-rubanau can you take a look and do sanity check whether there's anything we need to do besides just starting to merge to main instead of develop?

[hleb-rubanau]

@hleb-rubanau can you take a look and do sanity check whether there's anything we need to do besides just starting to merge to main instead of develop?

I think that’s absolutely fine, especially since publishing is handled manually.

The only thing worth keeping in mind is tracking published stable versions, and being ready (if development ever becomes nonlinear) to branch off dedicated “stable” lines for hotfixes. For example, if you need to patch an already released version while main has moved far ahead.

[hleb-rubanau]

@dividedmind from my side I don’t see any obstacles to approval, as long as you can confirm that hardcoding the instrumentation key is acceptable.

[dividedmind]

@hleb-rubanau can you take a look and do sanity check whether there's anything we need to do besides just starting to merge to main instead of develop?

I think that’s absolutely fine, especially since publishing is handled manually.

The only thing worth keeping in mind is tracking published stable versions, and being ready (if development ever becomes nonlinear) to branch off dedicated “stable” lines for hotfixes. For example, if you need to patch an already released version while main has moved far ahead.

Ok, I'm going to merge this to main and then let's merge any future changes directly there.

[appland-release]

🎉 This PR is included in version 0.81.0 🎉

The release is available on:

• v0.81.0
• GitHub release

Your semantic-release bot 📦🚀