New version: Grassmann v0.4.0

[JuliaRegistrator]

• Registering package: Grassmann
• Repository: https://github.com/chakravala/Grassmann.jl
• Created by: @chakravala
• Version: v0.4.0
• Commit: 4c9e7413d98359252f7ac49e623e130748039e2d
• Reviewed by: @chakravala
• Reference: chakravala/Grassmann.jl@4c9e741#commitcomment-36528528

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[dpsanders]

A useful tip is that if you install https://github.com/bcbi/CompatHelper.jl it will generate automated Pull Requests with suitable versions.

[noblock]

[chakravala]

[noblock] yes, I will start using CompatHelper soon, but am not using it yet at the moment

I am not in a rush to release anything at the moment

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: AbstractLattices, Combinatorics, ComputedFieldTypes, Leibniz, Requires, StaticArrays. You may find CompatHelper helpful for keeping your compat entries up-to-date.

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[github-actions]

Your new version pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: Combinatorics, Requires, StaticArrays. You may find CompatHelper helpful for keeping your compat entries up-to-date.

Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versionsyour package is compatible with. See [https://julialang.github.io/Pkg.jl/v1/compatibility/.] for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[DilumAluthge]

@chakravala

Next time, please add the compat entries. I recommend using CompatHelper.jl.