Skip to content

Commit

Permalink
Merge branch 'master' into v3.0.0-alpha
Browse files Browse the repository at this point in the history
  • Loading branch information
@quantum9Innovation
quantum9Innovation committed Nov 25, 2021
2 parents bbe229d + 6d7cf2f commit 535e0ee
Showing 1 changed file with 28 additions and 4 deletions.
32 changes: 28 additions & 4 deletions CHANGELOG.md
View file
Expand Up @@ -2,9 +2,9 @@

Latest stable release: 2.1.1\
Latest nightly release: 2.1.1.15\
Latest alpha release: 3.0.0-alpha-2
Latest alpha release: 3.0.0-alpha-3

Releases are listed from most recent to least recent. All `alpha` and in-development versions are released to the [epispot-nightly](https://pypi.org/project/epispot-nightly/) project while all other releases are shipped to the [main project](https://pypi.org/project/epispot/).
Releases are listed from most recent to least recent. All alpha and in-development versions are released to the [epispot-nightly](https://pypi.org/project/epispot-nightly/) project while all other releases are shipped to the [main project](https://pypi.org/project/epispot/).

---

Expand All @@ -15,14 +15,38 @@ Below is the official list of epispot versions and their support status. If we p
| Version | Patch | Bugfix | Security | Notes |
| ------- | ----- | ------ | -------- | ----- |
| 2.1 | 2.1.1 | ✔️ | ✔️ | Latest stable release |
| 2.0 | 2.0.2 | ✔️ | ✔️ |
| 2.0 | 2.0.2 | :x: | ✔️ |
| <= 1.1 | 1.1.0 | :x: | :x: | Deprecated |
| nightly latest | 2.1.1.15 | :x: | ✔️ |
| **3.0.0-alpha** | **3.0.0a2** | **✔️** | **✔️** | **Supported until beta release of v3** |
| **3.0.0-alpha** | **3.0.0a3** | **✔️** | **✔️** | **Supported until beta release of v3** |
| nightly < latest | 2.1.1.x | :x: | :x: | Deprecated |

---

## Release Schedule

For epispot v3.0.0:

| Release | Deadline | End of life |
| ------- | ------- | ----------- |
| v3.0.0-alpha-1 | N/A | 12/31/21 |
| v3.0.0-alpha-2 | N/A | 12/31/21 |
| v3.0.0-alpha-3 | 10/18/21 | 12/31/21 |
| v3.0.0-beta | 12/31/21 | 1/7/22 |
| v3.0.0 | 1/7/22 | LTS |

---

## 3.0.0-alpha-3

As the third release in the v3-alpha series, this version updates all dependencies and brings Python 3.10 support to epispot.

Epispot will now support all Python versions from 3.7 to 3.10, with our focus being on Python 3.10. [All dependencies have also been updated](https://github.com/epispot/epispot/pull/113) to ensure compatibility with Python 3.10 and to catch up on missed dependency updates from last release.

Additionally, in minor updates, epispot will be removing unnecessary CI checks (e.g. [DeepSource](https://github.com/epispot/epispot/commit/6119238737e088aceecb99c9bcfc57644f5c322f)) from analyzing non-package files and adding more [detailed summaries for Zenodo uploads](https://github.com/epispot/epispot/commit/95c99a82050e3ed20bdd73567e1d36b6c38bc766).

Finally, with this release comes a major update to epispot's security policy, which you can view [here](https://github.com/epispot/epispot/blob/master/SECURITY.md). This means that our entire organization will now follow the [Google OSS Vulnerability Guide](https://github.com/google/oss-vulnerability-guide), which will be applied for any security vulnerabilities we find in any epispot versions.

## 3.0.0-alpha-2 (standard-params)

This is the second stage of the v3 release rollout, following [v3.0.0-alpha-1](#300-alpha-1-massive-plots). The major change in this release revolves around solving issue [#73](https://github.com/epispot/epispot/issues/73), which completely redesigns epispot's internals.
Expand Down

4 comments on commit 535e0ee

@github-actions
Copy link

@github-actions github-actions bot commented on 535e0ee Nov 25, 2021 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

Unrecognized words, please review:

  • bdd
  • oss
  • patibility
Some files were were automatically ignored

These sample patterns would exclude them:

^SECURITY\.md$

You should consider adding them to:

.github/actions/spelling/excludes.txt

File matching is via Perl regular expressions.

To check these files, more of their words need to be in the dictionary than not. You can use patterns.txt to exclude portions, add items to the dictionary (e.g. by adding them to allow.txt), or fix typos.

To accept these unrecognized words as correct, run the following commands

... in a clone of the git@github.com:epispot/epispot.git repository
on the v3.0.0-alpha branch:

update_files() {
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
(cat '.github/actions/spelling/excludes.txt' - <<EOF
$should_exclude_patterns
EOF
) |grep .|
sort -f |
uniq > '.github/actions/spelling/excludes.txt.temp' &&
mv '.github/actions/spelling/excludes.txt.temp' '.github/actions/spelling/excludes.txt'
}

comment_json=$(mktemp)
curl -L -s -S \
  --header "Content-Type: application/json" \
  "https://api.github.com/repos/epispot/epispot/comments/60891265" > "$comment_json"
comment_body=$(mktemp)
jq -r .body < "$comment_json" > $comment_body
rm $comment_json

patch_add=$(perl -e '$/=undef;
$_=<>;
s{<details>.*}{}s;
s{^#.*}{};
s{\n##.*}{};
s{(?:^|\n)\s*\*}{}g;
s{\s+}{ }g;
print' < "$comment_body")
  

should_exclude_patterns=$(perl -e '$/=undef;
$_=<>;
exit unless s{(?:You should consider excluding directory paths|You should consider adding them to).*}{}s;
s{.*These sample patterns would exclude them:}{}s;
s{.*\`\`\`([^`]*)\`\`\`.*}{$1}m;
print' < "$comment_body" | grep . || true)

update_files
rm $comment_body
git add -u

@github-actions
Copy link

@github-actions github-actions bot commented on 535e0ee Nov 25, 2021 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

Unrecognized words, please review:

  • bdd
  • oss
  • patibility
Some files were were automatically ignored

These sample patterns would exclude them:

^SECURITY\.md$

You should consider adding them to:

.github/actions/spelling/excludes.txt

File matching is via Perl regular expressions.

To check these files, more of their words need to be in the dictionary than not. You can use patterns.txt to exclude portions, add items to the dictionary (e.g. by adding them to allow.txt), or fix typos.

To accept these unrecognized words as correct, run the following commands

... in a clone of the git@github.com:epispot/epispot.git repository
on the refs/tags/v3.0.0-alpha-3 branch:

update_files() {
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
(cat '.github/actions/spelling/excludes.txt' - <<EOF
$should_exclude_patterns
EOF
) |grep .|
sort -f |
uniq > '.github/actions/spelling/excludes.txt.temp' &&
mv '.github/actions/spelling/excludes.txt.temp' '.github/actions/spelling/excludes.txt'
}

comment_json=$(mktemp)
curl -L -s -S \
  --header "Content-Type: application/json" \
  "https://api.github.com/repos/epispot/epispot/comments/60892187" > "$comment_json"
comment_body=$(mktemp)
jq -r .body < "$comment_json" > $comment_body
rm $comment_json

patch_add=$(perl -e '$/=undef;
$_=<>;
s{<details>.*}{}s;
s{^#.*}{};
s{\n##.*}{};
s{(?:^|\n)\s*\*}{}g;
s{\s+}{ }g;
print' < "$comment_body")
  

should_exclude_patterns=$(perl -e '$/=undef;
$_=<>;
exit unless s{(?:You should consider excluding directory paths|You should consider adding them to).*}{}s;
s{.*These sample patterns would exclude them:}{}s;
s{.*\`\`\`([^`]*)\`\`\`.*}{$1}m;
print' < "$comment_body" | grep . || true)

update_files
rm $comment_body
git add -u

@github-actions
Copy link

@github-actions github-actions bot commented on 535e0ee Jun 14, 2022 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

🔴 Please review

Unrecognized words (3) 
bdd
oss
patibility
Available dictionaries could cover words not in the dictionary

cspell:python/python.txt (364) covers 3 of them
cspell:django/django.txt (2342) covers 2 of them
cspell:cpp/cpp.txt (104293) covers 2 of them
cspell:lua/lua.txt (391) covers 1 of them
cspell:golang/go.txt (7745) covers 1 of them
cspell:bash/bash-words.txt (22) covers 1 of them

Consider adding them using:

      with:
        extra_dictionaries:
          cspell:python/python.txt
          cspell:django/django.txt
          cspell:cpp/cpp.txt
          cspell:lua/lua.txt
          cspell:golang/go.txt
          cspell:bash/bash-words.txt

To stop checking additional dictionaries, add:

      with:
        check_extra_dictionaries: ''
Some files were automatically ignored

These sample patterns would exclude them:

^SECURITY\.md$

You should consider adding them to:

.github/actions/spelling/excludes.txt

File matching is via Perl regular expressions.

To check these files, more of their words need to be in the dictionary than not. You can use patterns.txt to exclude portions, add items to the dictionary (e.g. by adding them to allow.txt), or fix typos.

To accept these unrecognized words as correct, run the following commands

... in a clone of the git@github.com:epispot/epispot.git repository
on the v3.0.0-beta branch:

update_files() {
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
(cat '.github/actions/spelling/excludes.txt' - <<EOF
^SECURITY\.md$
EOF
) |grep .|
sort -f |
uniq > '.github/actions/spelling/excludes.txt.temp' &&
mv '.github/actions/spelling/excludes.txt.temp' '.github/actions/spelling/excludes.txt'
}

comment_json=$(mktemp)
curl -L -s -S \
  -H "Content-Type: application/json" \
  "https://api.github.com/repos/epispot/epispot/comments/76105530" > "$comment_json"
comment_body=$(mktemp)
jq -r ".body // empty" "$comment_json" > $comment_body
rm $comment_json

patch_add=$(perl -e '$/=undef; $_=<>; print "$1" if m{Unrecognized words[^<]*</summary>\n*```\n*([^<]*)```\n*</details>$}m;' < "$comment_body")
  
update_files
rm $comment_body
git add -u

@github-actions
Copy link

@github-actions github-actions bot commented on 535e0ee Jun 14, 2022 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

🔴 Please review

Unrecognized words (3) 
bdd
oss
patibility
Available dictionaries could cover words not in the dictionary

cspell:python/python.txt (364) covers 3 of them
cspell:django/django.txt (2342) covers 2 of them
cspell:cpp/cpp.txt (104293) covers 2 of them
cspell:lua/lua.txt (391) covers 1 of them
cspell:golang/go.txt (7745) covers 1 of them
cspell:bash/bash-words.txt (22) covers 1 of them

Consider adding them using:

      with:
        extra_dictionaries:
          cspell:python/python.txt
          cspell:django/django.txt
          cspell:cpp/cpp.txt
          cspell:lua/lua.txt
          cspell:golang/go.txt
          cspell:bash/bash-words.txt

To stop checking additional dictionaries, add:

      with:
        check_extra_dictionaries: ''
Some files were automatically ignored

These sample patterns would exclude them:

^SECURITY\.md$

You should consider adding them to:

.github/actions/spelling/excludes.txt

File matching is via Perl regular expressions.

To check these files, more of their words need to be in the dictionary than not. You can use patterns.txt to exclude portions, add items to the dictionary (e.g. by adding them to allow.txt), or fix typos.

To accept these unrecognized words as correct, run the following commands

... in a clone of the git@github.com:epispot/epispot.git repository
on the v3.0.0-beta branch:

update_files() {
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
(cat '.github/actions/spelling/excludes.txt' - <<EOF
^SECURITY\.md$
EOF
) |grep .|
sort -f |
uniq > '.github/actions/spelling/excludes.txt.temp' &&
mv '.github/actions/spelling/excludes.txt.temp' '.github/actions/spelling/excludes.txt'
}

comment_json=$(mktemp)
curl -L -s -S \
  -H "Content-Type: application/json" \
  "https://api.github.com/repos/epispot/epispot/comments/76106219" > "$comment_json"
comment_body=$(mktemp)
jq -r ".body // empty" "$comment_json" > $comment_body
rm $comment_json

patch_add=$(perl -e '$/=undef; $_=<>; print "$1" if m{Unrecognized words[^<]*</summary>\n*```\n*([^<]*)```\n*</details>$}m;' < "$comment_body")
  
update_files
rm $comment_body
git add -u

Please sign in to comment.