github2
`<https://github.com/Disfactory/DisfactoryMonthlyReport/commit/09f71ba0924f810d26d2285490953f85902b7891|09f71ba0>` - chore: autopublish 2022-05-01T01:42:59Z
disfactory-notification
Month: 2022-05
- 2020-09 (51)
- 2020-10 (92)
- 2020-11 (209)
- 2020-12 (97)
- 2021-01 (87)
- 2021-02 (160)
- 2021-03 (231)
- 2021-04 (149)
- 2021-05 (142)
- 2021-06 (115)
- 2021-07 (70)
- 2021-08 (62)
- 2021-09 (103)
- 2021-10 (148)
- 2021-11 (159)
- 2021-12 (134)
- 2022-01 (128)
- 2022-02 (214)
- 2022-03 (264)
- 2022-04 (531)
- 2022-05 (198)
- 2022-06 (108)
- 2022-07 (130)
- 2022-08 (243)
- 2022-09 (248)
- 2022-10 (120)
- 2022-11 (126)
- 2022-12 (130)
- 2023-01 (89)
- 2023-02 (103)
- 2023-03 (169)
- 2023-04 (84)
- 2023-05 (166)
- 2023-06 (143)
- 2023-07 (149)
- 2023-08 (107)
- 2023-09 (136)
- 2023-10 (100)
- 2023-11 (118)
- 2023-12 (102)
- 2024-01 (72)
- 2024-02 (70)
- 2024-03 (100)
- 2024-04 (88)
- 2024-05 (2)
- 2024-06 (31)
- 2024-07 (4)
- 2024-08 (6)
- 2024-09 (6)
- 2024-10 (40)
- 2024-11 (21)
2022-05-01
github2
<https://github.com/Disfactory/Disfactory/pull/602|#602 增加 factory location api>
這個 API 不需要除了 Factory table 的資料之外，不需要 Document 與 ReportRecord 的資訊 應該可以加快 SpotDiff 使用 Factory ID 取工廠位置資訊的速度， 並且減輕 server 負擔
github2
<https://github.com/Disfactory/Disfactory/pull/602|#602 增加 factory location api>
這個 API 不需要除了 Factory table 的資料之外，不需要 Document 與 ReportRecord 的資訊 應該可以加快 SpotDiff 使用 Factory ID 取工廠位置資訊的速度， 並且減輕 server 負擔
:white_check_mark: All checks have passed
github2
`<https://github.com/Disfactory/Disfactory/commit/a92f8abe523a7faeec3f125b46adb073612170d4|a92f8abe>` - upgrade python from 3.7 to 3.9 `<https://github.com/Disfactory/Disfactory/commit/f4f538be99fb4fc730b03a1c09c808174b51b9ee|f4f538be>` - add factory location api `<https://github.com/Disfactory/Disfactory/commit/4666e85acc68375cfa068ca97f6616c1d28a6341|4666e85a>` - Merge pull request #602 from Swind/factory_location_api
github2
`<https://github.com/Disfactory/Disfactory/commit/a92f8abe523a7faeec3f125b46adb073612170d4|a92f8abe>` - upgrade python from 3.7 to 3.9 `<https://github.com/Disfactory/Disfactory/commit/f4f538be99fb4fc730b03a1c09c808174b51b9ee|f4f538be>` - add factory location api `<https://github.com/Disfactory/Disfactory/commit/4666e85acc68375cfa068ca97f6616c1d28a6341|4666e85a>` - Merge pull request #602 from Swind/factory_location_api
github2
:white_check_mark: All checks have passed
github2
:white_check_mark: All checks have passed
github2
:white_check_mark: All checks have passed
github2
`<https://github.com/Disfactory/SpotDiffFrontend/commit/dcbe5de713097724f50d4c068e3d824965e987e5|dcbe5de7>` - feat: change api endpoint to improve fetch speed `<https://github.com/Disfactory/SpotDiffFrontend/commit/4a08d35d1deacd2d94336ada9439d2c4e0f9ed96|4a08d35d>` - Merge pull request #103 from Disfactory/0501-api-update
github2
`<https://github.com/Disfactory/SpotDiffFrontend/commit/dcbe5de713097724f50d4c068e3d824965e987e5|dcbe5de7>` - feat: change api endpoint to improve fetch speed `<https://github.com/Disfactory/SpotDiffFrontend/commit/4a08d35d1deacd2d94336ada9439d2c4e0f9ed96|4a08d35d>` - Merge pull request #103 from Disfactory/0501-api-update
2022-05-02
github2
<https://github.com/Disfactory/SpotDiffFrontend/pull/104|#104 Feature/67-leaflet-tile-filter>
resolve <https://github.com/Disfactory/SpotDiffFrontend/issues/67|#67>
github2
<https://github.com/Disfactory/SpotDiffFrontend/pull/104|#104 Feature/67-leaflet-tile-filter>
resolve <https://github.com/Disfactory/SpotDiffFrontend/issues/67|#67> <https://user-images.githubusercontent.com/4230968/166182883-e02fea6e-cf52-4888-981c-8b9f3056a11f.png|スクリーンショット 2022-05-02 午後12 04 35>
:white_check_mark: All checks have passed
github2
:white_check_mark: All checks have passed
2022-05-03
2022-05-04
github2
*Is your feature request related to a problem? Please describe.* ：有沒有擴建，比較難，因為我常過度聚焦在看準心處，沒有看整體，就回答了，於是下一張問有無擴建時，只能瞎猜。 ：圈起來的地方可以切換before and after~ ：原來如此！教學沒有提示，還以為只是在告知before/after，不知可以切換。感謝。 ：deepr使用者回饋～我一開始玩也沒注意到before and after *Describe the solution you'd like* Add an introduction of the switch to the "learning session." *Describe alternatives you've considered* Redesign the before/after button so that users could notice it easily. *Additional context* I've also remind a friend to use the button when he reach the third question and couldn't make a decision.
github2
*Is your feature request related to a problem? Please describe.* ：有沒有擴建，比較難，因為我常過度聚焦在看準心處，沒有看整體，就回答了，於是下一張問有無擴建時，只能瞎猜。 ：圈起來的地方可以切換before and after~ ：原來如此！教學沒有提示，還以為只是在告知before/after，不知可以切換。感謝。 ：deepr使用者回饋～我一開始玩也沒注意到before and after *Describe the solution you'd like* Add an introduction of the button to the "learning session." *Describe alternatives you've considered* Redesign the before/after button so that users could notice it easily. *Additional context* I've also remind a friend to use the button when he reach the third question and couldn't make a decision.
github2
*Expected Behavior* Users can clearly know the range they should identify is the space inside the red box. *Current Behavior* Users are confused about the new building outside the box. *Possible Solution* Change the text of second question of "建物" to "承上，你覺得after的方框內有擴建嗎？" *Screenshots* <https://user-images.githubusercontent.com/60970217/166666460-21c73fd3-dd11-4569-815f-a3c0e94f1ee2.jpg|Image from iOS (1)> <https://user-images.githubusercontent.com/60970217/166666444-df335b6a-fc2f-4b60-9928-aaf6bb64b92d.jpg|Image from iOS>
github2
*Expected Behavior* Users can clearly know the range they should identify is the space inside the red box. *Current Behavior* Users are confused about the new building outside the box. *Possible Solution* Change the text of second question of "建物" to "承上，你覺得after的方框內有擴建嗎？" *Screenshots* <https://user-images.githubusercontent.com/60970217/166666460-21c73fd3-dd11-4569-815f-a3c0e94f1ee2.jpg|Image from iOS (1)> <https://user-images.githubusercontent.com/60970217/166666444-df335b6a-fc2f-4b60-9928-aaf6bb64b92d.jpg|Image from iOS>
github2
`<https://github.com/Disfactory/about.disfactory.tw/commit/5b8d997023698f2e46efb3308223ebb6b5b6fc7d|5b8d9970>` - feat: update NavigationHeader `<https://github.com/Disfactory/about.disfactory.tw/commit/ddbbcfcd21534e8134b1f250f83166ad8dd636e0|ddbbcfcd>` - feat(dactoryDisplay): remove button of compitition `<https://github.com/Disfactory/about.disfactory.tw/commit/051252122fa1530c61cc2e21b8e66e0a33543702|05125212>` - feat: add button of go to spotdiff in slide manu `<https://github.com/Disfactory/about.disfactory.tw/commit/993b9de5b38f82a87a582c352faed1ec764d737a|993b9de5>` - feat: update ui of tutorial `<https://github.com/Disfactory/about.disfactory.tw/commit/6d900e7c513a37a251eb884c05156c806098a647|6d900e7c>` - Merge pull request #83 from Disfactory/0504-ui
github2
`<https://github.com/Disfactory/about.disfactory.tw/commit/5b8d997023698f2e46efb3308223ebb6b5b6fc7d|5b8d9970>` - feat: update NavigationHeader `<https://github.com/Disfactory/about.disfactory.tw/commit/ddbbcfcd21534e8134b1f250f83166ad8dd636e0|ddbbcfcd>` - feat(dactoryDisplay): remove button of compitition `<https://github.com/Disfactory/about.disfactory.tw/commit/051252122fa1530c61cc2e21b8e66e0a33543702|05125212>` - feat: add button of go to spotdiff in slide manu `<https://github.com/Disfactory/about.disfactory.tw/commit/993b9de5b38f82a87a582c352faed1ec764d737a|993b9de5>` - feat: update ui of tutorial `<https://github.com/Disfactory/about.disfactory.tw/commit/6d900e7c513a37a251eb884c05156c806098a647|6d900e7c>` - Merge pull request #83 from Disfactory/0504-ui
github2
`<https://github.com/Disfactory/about.disfactory.tw/commit/b7a4f6febf5d9a1236a51ab4b88b3d20c27c7b1c|b7a4f6fe>` - update 貢獻者 (contributor list) `<https://github.com/Disfactory/about.disfactory.tw/commit/dc114780de6c5aa56001048db83b14c2ab211944|dc114780>` - style: format by prettier `<https://github.com/Disfactory/about.disfactory.tw/commit/85c8176ad1b4188528937fcfd222e6d50ec4fcfb|85c8176a>` - Merge pull request #82 from Disfactory/ael-patch-contributors
github2
`<https://github.com/Disfactory/about.disfactory.tw/commit/b7a4f6febf5d9a1236a51ab4b88b3d20c27c7b1c|b7a4f6fe>` - update 貢獻者 (contributor list) `<https://github.com/Disfactory/about.disfactory.tw/commit/dc114780de6c5aa56001048db83b14c2ab211944|dc114780>` - style: format by prettier `<https://github.com/Disfactory/about.disfactory.tw/commit/85c8176ad1b4188528937fcfd222e6d50ec4fcfb|85c8176a>` - Merge pull request #82 from Disfactory/ael-patch-contributors
2022-05-05
github2
:white_check_mark: All checks have passed
github2
<https://github.com/Disfactory/SpotDiffFrontend/pull/109|#109 chore: merge main into production>
:white_check_mark: All checks have passed
github2
<https://github.com/Disfactory/SpotDiffFrontend/pull/110|#110 chore: merge main into production>
:white_check_mark: All checks have passed
2022-05-06
2022-05-07
2022-05-11
github2
<https://github.com/Disfactory/Disfactory/pull/603|#603 fix proxy schema>
看起來應該是因為 requests 更新設定方式 現在需要指定 schema
:white_check_mark: All checks have passed
github2
<https://github.com/Disfactory/Disfactory/pull/603|#603 fix proxy schema>
看起來應該是因為 requests 更新設定方式 現在需要指定 schema
github2
*Is your feature request related to a problem? Please describe.* 增加使用者的榮譽感 *Describe the solution you'd like* 呈現已有多少答案給使用者看 設計圖：<https://www.figma.com/file/TVAEC28E3ojabGHc8BawbI/%E8%A1%9B%E6%98%9F%E7%A9%BA%E7%85%A7%E5%9C%96?node-id=0%3A2|https://www.figma.com/file/TVAEC28E3ojabGHc8BawbI/%E8%A1%9B%E6%98%9F%E7%A9%BA%E7%85%A7%E5%9C%96?node-id=0%3A2> 有任何問題可再在figma上留言討論
github2
*Is your feature request related to a problem? Please describe.* 增加使用者的榮譽感 *Describe the solution you'd like* 呈現已有多少答案給使用者看 設計圖：<https://www.figma.com/file/TVAEC28E3ojabGHc8BawbI/%E8%A1%9B%E6%98%9F%E7%A9%BA%E7%85%A7%E5%9C%96?node-id=0%3A2|https://www.figma.com/file/TVAEC28E3ojabGHc8BawbI/%E8%A1%9B%E6%98%9F%E7%A9%BA%E7%85%A7%E5%9C%96?node-id=0%3A2> 有任何問題可再在figma上留言討論
2022-05-12
github2
<https://github.com/Disfactory/SpotDiffFrontend/pull/112|#112 feat(loading): show alert text>
:white_check_mark: All checks have passed
2022-05-13
github2
<https://github.com/Disfactory/DisfactoryMonthlyReport/issues/1|#1 系統計算結果和自行計算結果出現落差>
剛剛用action跑了一次產出統計的workflow 出了檢舉的總數是533，但django和about page縣市都是547 所以用vlookup統計了一次輸出的document table 結果只有「已發函斷電」、「已排程拆除」、「已拆除」數字是一致的，其他都出現1~5不等的落差。 還不知道原因是什麼，只是先放issue～ 剛用github輸出的 <https://user-images.githubusercontent.com/60970217/168213828-1c9a0ce9-d094-41e6-a0d0-37b0821092bc.png|截圖 2022-05-13 下午12 55 52> 自己輸出document table用vlookup算的 <https://user-images.githubusercontent.com/60970217/168213896-8b5f83d9-d1d2-4630-b874-2d651f699d1a.png|截圖 2022-05-13 下午12 56 35>
github2
<https://github.com/Disfactory/DisfactoryMonthlyReport/issues/1|#1 系統計算結果和自行計算結果出現落差>
剛剛用action跑了一次產出統計的workflow 出了檢舉的總數是533，但django和about page縣市都是547 所以用vlookup統計了一次輸出的document table 結果只有「已發函斷電」、「已排程拆除」、「已拆除」數字是一致的，其他都出現1~5不等的落差。 還不知道原因是什麼，只是先放issue～ 剛用github輸出的 <https://user-images.githubusercontent.com/60970217/168213828-1c9a0ce9-d094-41e6-a0d0-37b0821092bc.png|截圖 2022-05-13 下午12 55 52> 自己輸出document table用vlookup算的 <https://user-images.githubusercontent.com/60970217/168213896-8b5f83d9-d1d2-4630-b874-2d651f699d1a.png|截圖 2022-05-13 下午12 56 35>
2022-05-14
2022-05-16
github2
:white_check_mark: All checks have passed
github2
:white_check_mark: All checks have passed
2022-05-17
github2
Bumps <https://github.com/postcss/postcss|postcss> from 7.0.27 to 7.0.39. Release notes _Sourced from <https://github.com/postcss/postcss/releases|postcss's releases>._ > *7.0.39* > > • Reduce package size. > • Backport `nanocolors` to `picocolors` migration. > > *7.0.38* > > • Update `Processor#version`. > > *7.0.37* > > • Backport `chalk` to `nanocolors` migration. > > *7.0.36* > > • Backport ReDoS vulnerabilities from PostCSS 8. > > *7.0.35* > > • Add <https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users|migration guide link> to PostCSS 8 error text. > > *7.0.34* > > • Fix compatibility with `postcss-scss` 2. > > *7.0.33* > > • Add error message for PostCSS 8 plugins. > > *7.0.32* > > • Fix error message (by <https://github.com/admosity|`@admosity`>). > > *7.0.31* > > • Use only the latest source map annotation (by <https://github.com/emzoumpo|`@emzoumpo`>). > > *7.0.30* > > • Fix TypeScript definition (by <https://github.com/nex3|`@nex3`>) > > *7.0.29* > > • Update `Processor#version`. > > *7.0.28* > > • Fix TypeScript definition (by <https://github.com/nex3|`@nex3`>). Changelog _Sourced from <https://github.com/postcss/postcss/blob/7.0.39/CHANGELOG.md|postcss's changelog>._ > *7.0.39* > > • Reduce package size. > • Backport `nanocolors` to `picocolors` migration. > > *7.0.38* > > • Update `Processor#version`. > > *7.0.37* > > • Backport `chalk` to `nanocolors` migration. > > *7.0.36* > > • Backport ReDoS vulnerabilities from PostCSS 8. > > *7.0.35* > > • Add migration guide link to PostCSS 8 error text. > > *7.0.34* > > • Fix compatibility with `postcss-scss` 2. > > *7.0.33* > > • Add error message for PostCSS 8 plugins. > > *7.0.32* > > • Fix error message (by <https://github.com/admosity|`@admosity`>). > > *7.0.31* > > • Use only the latest source map annotation (by Emmanouil Zoumpoulakis). > > *7.0.30* > > • Fix TypeScript definition (by Natalie Weizenbaum). > > *7.0.29* > > • Update `Processor#version`. > > *7.0.28* > > • Fix TypeScript definition (by Natalie Weizenbaum). Commits • <https://github.com/postcss/postcss/commit/e17c1ef7623a71be5732432ca8499bc9928aa08d|`e17c1ef`> Release 7.0.39 version • <https://github.com/postcss/postcss/commit/6791bd3d5f7ab27ad36dc075033a5beb4bdbfe9e|`6791bd3`> Reduce npm package • <https://github.com/postcss/postcss/commit/44c581a55a9aab339ee319aa67c264b02c4a6448|`44c581a`> Replace nanocolors with picocolors • <https://github.com/postcss/postcss/commit/8ba21fd8f4c3bff146b8a71d2d12f31435444394|`8ba21fd`> Remove eslint-ci • <https://github.com/postcss/postcss/commit/3994c4aa3ce1835c9b36ae17ab94e45c21b56fb2|`3994c4a`> Release 7.0.38 version • <https://github.com/postcss/postcss/commit/6944e1dd808da66cee4ebf287c66c6aa0fc5c2a0|`6944e1d`> Remove development keys from package.json • <https://github.com/postcss/postcss/commit/4dd0af024a915bd12d2d53990c5a4fa4129563d5|`4dd0af0`> Release 7.0.37 version • <https://github.com/postcss/postcss/commit/8408eb4105755c43dbf09a000fd2f1308f240232|`8408eb4`> Add compilation step • <https://github.com/postcss/postcss/commit/0c680639c3d717b4c8c0b2b2a9d1799fbf239a76|`0c68063`> Move tests to GitHub Actions • <https://github.com/postcss/postcss/commit/98b61ba5b46622de48bb2592583757ab846212ad|`98b61ba`> Replace chalk to nanocolors • Additional commits viewable in <https://github.com/postcss/postcss/compare/7.0.27...7.0.39|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
github2
Bumps <https://github.com/postcss/postcss|postcss> from 7.0.27 to 7.0.39. Release notes _Sourced from <https://github.com/postcss/postcss/releases|postcss's releases>._ > *7.0.39* > > • Reduce package size. > • Backport `nanocolors` to `picocolors` migration. > > *7.0.38* > > • Update `Processor#version`. > > *7.0.37* > > • Backport `chalk` to `nanocolors` migration. > > *7.0.36* > > • Backport ReDoS vulnerabilities from PostCSS 8. > > *7.0.35* > > • Add <https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users|migration guide link> to PostCSS 8 error text. > > *7.0.34* > > • Fix compatibility with `postcss-scss` 2. > > *7.0.33* > > • Add error message for PostCSS 8 plugins. > > *7.0.32* > > • Fix error message (by <https://github.com/admosity|`@admosity`>). > > *7.0.31* > > • Use only the latest source map annotation (by <https://github.com/emzoumpo|`@emzoumpo`>). > > *7.0.30* > > • Fix TypeScript definition (by <https://github.com/nex3|`@nex3`>) > > *7.0.29* > > • Update `Processor#version`. > > *7.0.28* > > • Fix TypeScript definition (by <https://github.com/nex3|`@nex3`>). Changelog _Sourced from <https://github.com/postcss/postcss/blob/7.0.39/CHANGELOG.md|postcss's changelog>._ > *7.0.39* > > • Reduce package size. > • Backport `nanocolors` to `picocolors` migration. > > *7.0.38* > > • Update `Processor#version`. > > *7.0.37* > > • Backport `chalk` to `nanocolors` migration. > > *7.0.36* > > • Backport ReDoS vulnerabilities from PostCSS 8. > > *7.0.35* > > • Add migration guide link to PostCSS 8 error text. > > *7.0.34* > > • Fix compatibility with `postcss-scss` 2. > > *7.0.33* > > • Add error message for PostCSS 8 plugins. > > *7.0.32* > > • Fix error message (by <https://github.com/admosity|`@admosity`>). > > *7.0.31* > > • Use only the latest source map annotation (by Emmanouil Zoumpoulakis). > > *7.0.30* > > • Fix TypeScript definition (by Natalie Weizenbaum). > > *7.0.29* > > • Update `Processor#version`. > > *7.0.28* > > • Fix TypeScript definition (by Natalie Weizenbaum). Commits • <https://github.com/postcss/postcss/commit/e17c1ef7623a71be5732432ca8499bc9928aa08d|`e17c1ef`> Release 7.0.39 version • <https://github.com/postcss/postcss/commit/6791bd3d5f7ab27ad36dc075033a5beb4bdbfe9e|`6791bd3`> Reduce npm package • <https://github.com/postcss/postcss/commit/44c581a55a9aab339ee319aa67c264b02c4a6448|`44c581a`> Replace nanocolors with picocolors • <https://github.com/postcss/postcss/commit/8ba21fd8f4c3bff146b8a71d2d12f31435444394|`8ba21fd`> Remove eslint-ci • <https://github.com/postcss/postcss/commit/3994c4aa3ce1835c9b36ae17ab94e45c21b56fb2|`3994c4a`> Release 7.0.38 version • <https://github.com/postcss/postcss/commit/6944e1dd808da66cee4ebf287c66c6aa0fc5c2a0|`6944e1d`> Remove development keys from package.json • <https://github.com/postcss/postcss/commit/4dd0af024a915bd12d2d53990c5a4fa4129563d5|`4dd0af0`> Release 7.0.37 version • <https://github.com/postcss/postcss/commit/8408eb4105755c43dbf09a000fd2f1308f240232|`8408eb4`> Add compilation step • <https://github.com/postcss/postcss/commit/0c680639c3d717b4c8c0b2b2a9d1799fbf239a76|`0c68063`> Move tests to GitHub Actions • <https://github.com/postcss/postcss/commit/98b61ba5b46622de48bb2592583757ab846212ad|`98b61ba`> Replace chalk to nanocolors • Additional commits viewable in <https://github.com/postcss/postcss/compare/7.0.27...7.0.39|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
github2
Bumps <https://github.com/Qix-/color-string|color-string> from 1.5.3 to 1.9.1. Release notes _Sourced from <https://github.com/Qix-/color-string/releases|color-string's releases>._ > *1.9.0* > *Minor Release 1.9.0* > > • Add parsing of exponential alpha values for HWB and HSL (<https://github.com/Qix-/color-string/issues/66|#66>) > > Thanks to <https://github.com/babycannotsay|`@babycannotsay`> for their contribution! > > *1.8.2* > *Patch release 1.8.2* > > • Fix incorrect handling of optional comma in rgb() regex (<https://github.com/Qix-/color-string/issues/65|#65>) > > Thanks to <https://github.com/gerdasi|`@gerdasi`> and <https://github.com/mastertheblaster|`@mastertheblaster`> for reporting and confirming the bug! > > *1.8.1* > *Patch release 1.8.1* > > • Fix rgb alpha percentage parsing from int to float (<https://github.com/Qix-/color-string/issues/61|#61>) > > Thanks to <https://github.com/clytras|`@clytras`> for their contribution! > > *1.8.0* > *Minor release 1.8.0* > > • Add anchors to keyword regex (<https://github.com/Qix-/color-string/issues/64|#64>) > > Thanks to <https://github.com/cq360767996|`@cq360767996`> for their contribution! > > *1.7.4* > *Patch Release 1.7.4* > > • Fix bug in `.to.hex()` output if the inputs aren't rounded numbers (<https://github.com/Qix-/color-string/issues/25|#25>) > > *1.7.3* > *Patch Release 1.7.3* > > • Fix hue modulo operation (<https://github.com/Qix-/color-string/issues/50|#50>) > > Thanks to <https://github.com/adroitwhiz|`@adroitwhiz`> for their contributions. > > *1.7.2* > *Patch Release 1.7.2* > > • Fix issue where color-string with incorrectly return a color for properties on Object's prototype like "constructor". (<https://github.com/Qix-/color-string/issues/45|#45>) > > Thanks to <https://github.com/tolmasky|`@tolmasky`> for their contributions. > > *1.7.1* > *Patch release 1.7.1* ... (truncated) Commits • See full diff in <https://github.com/Qix-/color-string/commits/1.9.1|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
github2
Bumps <https://github.com/Qix-/color-string|color-string> from 1.5.3 to 1.9.1. Release notes _Sourced from <https://github.com/Qix-/color-string/releases|color-string's releases>._ > *1.9.0* > *Minor Release 1.9.0* > > • Add parsing of exponential alpha values for HWB and HSL (<https://github.com/Qix-/color-string/issues/66|#66>) > > Thanks to <https://github.com/babycannotsay|`@babycannotsay`> for their contribution! > > *1.8.2* > *Patch release 1.8.2* > > • Fix incorrect handling of optional comma in rgb() regex (<https://github.com/Qix-/color-string/issues/65|#65>) > > Thanks to <https://github.com/gerdasi|`@gerdasi`> and <https://github.com/mastertheblaster|`@mastertheblaster`> for reporting and confirming the bug! > > *1.8.1* > *Patch release 1.8.1* > > • Fix rgb alpha percentage parsing from int to float (<https://github.com/Qix-/color-string/issues/61|#61>) > > Thanks to <https://github.com/clytras|`@clytras`> for their contribution! > > *1.8.0* > *Minor release 1.8.0* > > • Add anchors to keyword regex (<https://github.com/Qix-/color-string/issues/64|#64>) > > Thanks to <https://github.com/cq360767996|`@cq360767996`> for their contribution! > > *1.7.4* > *Patch Release 1.7.4* > > • Fix bug in `.to.hex()` output if the inputs aren't rounded numbers (<https://github.com/Qix-/color-string/issues/25|#25>) > > *1.7.3* > *Patch Release 1.7.3* > > • Fix hue modulo operation (<https://github.com/Qix-/color-string/issues/50|#50>) > > Thanks to <https://github.com/adroitwhiz|`@adroitwhiz`> for their contributions. > > *1.7.2* > *Patch Release 1.7.2* > > • Fix issue where color-string with incorrectly return a color for properties on Object's prototype like "constructor". (<https://github.com/Qix-/color-string/issues/45|#45>) > > Thanks to <https://github.com/tolmasky|`@tolmasky`> for their contributions. > > *1.7.1* > *Patch release 1.7.1* ... (truncated) Commits • See full diff in <https://github.com/Qix-/color-string/commits/1.9.1|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
2022-05-20
2022-05-21
2022-05-23
2022-05-24
2022-05-25
2022-05-27
2022-05-29
2022-05-31