Increment webapp version from 0.3.0 -> 0.3.1

[shrishrirang]

• The 0.3.0 release didn't happen because of "azdev style webapp" errors
• Incrementing 0.3.0->0.3.1 to kick-off another release

---

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[yonzhan]

webapp

[yungezz]

hi @qwordy could you pls give this a quick review?

[qwordy]

I have not seen any code change. How does it get passed while #2781 fails?
No problem to use 0.3.1. I am OK.

[shrishrirang]

The first PR that incremented the version to 0.3.0 was #2768 and it had some style errors.
The second PR #2811 fixed those errors. This PR is just a follow-up PR that bumps up the version from 0.3.0 to 0.3.1, but the actual code changes that fixed the style errors are already merged.

[qwordy]

The first PR that incremented the version to 0.3.0 was #2768 and it had some style errors.
The second PR #2811 fixed those errors. This PR is just a follow-up PR that bumps up the version from 0.3.0 to 0.3.1, but the actual code changes that fixed the style errors are already merged.

Got it

[shrishrirang]

I don't see a new release triggered for the new version 0.3.1 in this PR. The last PR I see is still for 0.3.0 - #2781. Can you check why is that so and trigger a run manually? Also, #2781 should be closed.

[qwordy]

@haroldrandom Can you help have a look? What is the rule to trigger a release PR?

[qwordy]

I have closed the old PR 2781

[shrishrirang]

@haroldrandom - any idea why this PR didn't release the extension? Can we trigger a manual run of the pipeline if it wasn't automatically triggered for some reason?