We are currently solving the following issue within our repository. Here is the issue text:
--- BEGIN ISSUE ---
Parsl v1.1.0 Release Checklist
## Checklist

Please edit the checklist if I've missed any items. 

### Documentation updates :

- [x] Update docs to point at 1.1.0 as the latest
- [x] Make sure docs are not broken on readthedocs, since a broken doc build will stick on as stable till next release.
- [x] Update changelog with summary of changes since 0.9.0 [@benclifford to take a crack at this]
- [ ] Update Parsl tutorial repo with a 1.1.0 branch that folds in changes 
- [x] Add `Beta` tags to components/features that are not yet stable.


### Testing :

- [ ] All testing should be green on Travis
- [x] Update all configs in `parsl/parsl/configs` to match current best practices
- [x] Update all test configs in `parsl/parsl/test/configs`
- [x] Test notebooks/tutorials and basic tests on a Mac
- [ ] Post news update on the website about release

- [x] Site testing:
  - [x] Bridges2(PSC) [YY]
  - [ ] ~~Comet (SDSC)~~ Machine is getting replaced by Expanse
  - [x] Cori (NERSC) [YY/Yadu]
  - [x] Stampede2 (TACC) [Yadu]
  - [ ] ~~Frontera (TACC)~~ [Yadu, no access]
  - [x] Theta (ALCF) [YY]
  - [x] Bluewaters (NCSA) [ZZ]
  - [x] Summit (ORNL) [Yadu]
  - [ ] ~~CC-IN2P3 (French Grid)~~ [Yadu]
  - [x] Midway (RCC, UChicago) [YY]
  - [x] Open Science Grid
  - [x] AWS
  - [x] Kubernetes [ZZ]
  - [x] NSCC Singapore [ZZ]
  - [ ] Ad-Hoc clusters [YY]

### Release Tagging and pushing to PyPI

I'll make an updated alpha to smoothen installation and site testing.


--- END ISSUE ---

Below are some code segments, each from a relevant file. One or more of these files may contain bugs.
--- BEGIN FILES ---
Path: `parsl/version.py`
Content:
```
1 """Set module version.
2 
3 <Major>.<Minor>.<maintenance>[alpha/beta/..]
4 Alphas will be numbered like this -> 0.4.0a0
5 """
6 VERSION = '1.1.0a1'
7
```
--- END FILES ---

Please first localize the bug based on the issue statement, and then generate a patch according to the `git diff` format fenced by three backticks.

Here is an example:

```diff
diff --git a/examples/server_async.py b/examples/server_async.py
--- a/examples/server_async.py
+++ b/examples/server_async.py
@@ -313,4 +313,4 @@
 
 
 if __name__ == "__main__":
-    asyncio.run(run_async_server("."), debug=True)
+    asyncio.run(run_async_server(), debug=True)
diff --git a/examples/server_sync.py b/examples/server_sync.py
--- a/examples/server_sync.py
+++ b/examples/server_sync.py
@@ -313,5 +313,5 @@
 
 
 if __name__ == "__main__":
-    server = run_sync_server(".")
+    server = run_sync_server()
     server.shutdown()

```

diff --git a/parsl/version.py b/parsl/version.py
--- a/parsl/version.py
+++ b/parsl/version.py
@@ -3,4 +3,4 @@
 <Major>.<Minor>.<maintenance>[alpha/beta/..]
 Alphas will be numbered like this -> 0.4.0a0
 """
-VERSION = '1.1.0a1'
+VERSION = '1.1.0'

{"golden_diff": "diff --git a/parsl/version.py b/parsl/version.py\n--- a/parsl/version.py\n+++ b/parsl/version.py\n@@ -3,4 +3,4 @@\n <Major>.<Minor>.<maintenance>[alpha/beta/..]\n Alphas will be numbered like this -> 0.4.0a0\n \"\"\"\n-VERSION = '1.1.0a1'\n+VERSION = '1.1.0'\n", "issue": "Parsl v1.1.0 Release Checklist\n## Checklist\r\n\r\nPlease edit the checklist if I've missed any items. \r\n\r\n### Documentation updates :\r\n\r\n- [x] Update docs to point at 1.1.0 as the latest\r\n- [x] Make sure docs are not broken on readthedocs, since a broken doc build will stick on as stable till next release.\r\n- [x] Update changelog with summary of changes since 0.9.0 [@benclifford to take a crack at this]\r\n- [ ] Update Parsl tutorial repo with a 1.1.0 branch that folds in changes \r\n- [x] Add `Beta` tags to components/features that are not yet stable.\r\n\r\n\r\n### Testing :\r\n\r\n- [ ] All testing should be green on Travis\r\n- [x] Update all configs in `parsl/parsl/configs` to match current best practices\r\n- [x] Update all test configs in `parsl/parsl/test/configs`\r\n- [x] Test notebooks/tutorials and basic tests on a Mac\r\n- [ ] Post news update on the website about release\r\n\r\n- [x] Site testing:\r\n  - [x] Bridges2(PSC) [YY]\r\n  - [ ] ~~Comet (SDSC)~~ Machine is getting replaced by Expanse\r\n  - [x] Cori (NERSC) [YY/Yadu]\r\n  - [x] Stampede2 (TACC) [Yadu]\r\n  - [ ] ~~Frontera (TACC)~~ [Yadu, no access]\r\n  - [x] Theta (ALCF) [YY]\r\n  - [x] Bluewaters (NCSA) [ZZ]\r\n  - [x] Summit (ORNL) [Yadu]\r\n  - [ ] ~~CC-IN2P3 (French Grid)~~ [Yadu]\r\n  - [x] Midway (RCC, UChicago) [YY]\r\n  - [x] Open Science Grid\r\n  - [x] AWS\r\n  - [x] Kubernetes [ZZ]\r\n  - [x] NSCC Singapore [ZZ]\r\n  - [ ] Ad-Hoc clusters [YY]\r\n\r\n### Release Tagging and pushing to PyPI\r\n\r\nI'll make an updated alpha to smoothen installation and site testing.\r\n\n", "before_files": [{"content": "\"\"\"Set module version.\n\n<Major>.<Minor>.<maintenance>[alpha/beta/..]\nAlphas will be numbered like this -> 0.4.0a0\n\"\"\"\nVERSION = '1.1.0a1'\n", "path": "parsl/version.py"}], "after_files": [{"content": "\"\"\"Set module version.\n\n<Major>.<Minor>.<maintenance>[alpha/beta/..]\nAlphas will be numbered like this -> 0.4.0a0\n\"\"\"\nVERSION = '1.1.0'\n", "path": "parsl/version.py"}]}