update changelog for the next release (0.7.0)

[mapix]

For better code quality, it's advisable to fix the tests before merging this PR:

• [ ] https://github.com/fohrloop/dash-uploader/pull/136

Also, ensure that development dependencies remain consistent with the release environment:

• [ ] https://github.com/fohrloop/dash-uploader/pull/137

[mapix]

@fohrloop Please help confirm if these preparations are sufficient for releasing the next version. If anything else is needed, please list it. Since it might be better to update the specific version number at the time of release, I have not updated the version number.

[fohrloop]

Hi @mapix and thank you for creating the PR!

I think the description of this PR has a mistake as this does not fix issue 111 or issue 133, but updates the changelog. There's another file change in tests/test_uploading_same_file_twice_with_errors.py which skips a test to make the tests work on linux/macos. Could you please split the PR into two as it's addressing two things?

1. Updating Changelog
2. Fixing tests on macos/linux

about next release: dash-uploader 0.7.0

• As the previous release was a pre-release (0.7.0-a1), I suggest we remove the title "0.7.0-a1 (2022-03-30)" from the changelog and replace it with "0.7.0 (unreleased)". In other words, let's aggregate the pre-release release notes with the 0.7.0 release notes, because people reading just the 0.7.0 release notes could accidentally miss what's new or changed.
• It mentions that https://github.com/fohrloop/dash-uploader/pull/128 fixed #111, but it seems that it only fixes the issue when installing with the [dev] extras. I think the fix should be changing this line in the setup.py:

    install_requires=["dash>=1.1.0", "packaging>= 21.0"],

to

    install_requires=["dash>=1.1.0", "packaging>22"],

if a fix is provided, let's put that also through a separate PR (one PR per a thing).

[GitHunter0]

Hey @mapix , just checking with you, have you seen the @fohrloop feedback?

I'm really hoping for the next dash-uploader release, specially due to the packaging version requirement.

[mapix]

@fohrloop

Thanks for your advice. I missed this PR as I'm recently between jobs. I have followed your advice and separated all sub-PRs. Except for the packaging version, which I tested with 21.0 that everything works on the current codebase.

[fohrloop]

@mapix thanks a lot! I think we can keep this PR open until all the changes coming to the next releases are merged, and then have a final touch on the changelog.

Do you think it would make sense to update some of the JS packages before the release? My npm audit shows:

39 vulnerabilities (8 moderate, 25 high, 6 critical)

which looks a bit worrying to me. Or what do you think? There's also quite a list of outdated JS packages shown by npm outdated. What's your JS skill level?