Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the effect group across 1 directory with 3 updates #219

Closed
wants to merge 1 commit into from
Closed

Bump the effect group across 1 directory with 3 updates #219

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 10, 2024 •
edited
Loading

Bumps the effect group with 3 updates in the / directory: @effect/platform, @effect/schema and effect.

Updates @effect/platform from 0.49.3 to 0.57.0

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.57.0

Minor Changes

Patch Changes

@​effect/platform-node@​0.51.8

Patch Changes

@​effect/platform@​0.56.0

Minor Changes

Patch Changes

@​effect/platform-node@​0.51.7

Patch Changes

  • Updated dependencies [a67d602]:
    • @​effect/platform@​0.55.7
    • @​effect/platform-node-shared@​0.6.7

@​effect/platform@​0.55.7

Patch Changes

@​effect/platform-node@​0.51.6

Patch Changes

... (truncated)

Changelog

Sourced from @​effect/platform's changelog.

0.57.0

Minor Changes

Patch Changes

0.56.0

Minor Changes

Patch Changes

0.55.7

Patch Changes

0.55.6

Patch Changes

  • #2903 799aa20 Thanks @​rocwang! - # Make baseUrl() more defensive in @​effect/platform

    Sometimes, third party code may patch a missing global location to accommodate for non-browser JavaScript runtimes, e.g. Cloudflare Workers, Deno. Such patch might not yield a fully valid location. This could break baseUrl(), which is called by makeUrl().

    For example, the following code would log Invalid URL: '/api/v1/users' with base 'NaN'.

    

    • 






... (truncated)





Commits






Updates @effect/schema from 0.66.1 to 0.67.22



Release notes

Sourced from @​effect/schema's releases.




@​effect/schema@​0.67.22


Patch Changes



@​effect/schema@​0.67.21


Patch Changes



@​effect/schema@​0.67.20


Patch Changes


    

  • 

    #2926 4c6bc7f Thanks @​gcanti! - Add propertyOrder option to ParseOptions to control the order of keys in the output, closes #2925.
    

    The propertyOrder option provides control over the order of object fields in the output. This feature is particularly useful when the sequence of keys is important for the consuming processes or when maintaining the input order enhances readability and usability.
    

    By default, the propertyOrder option is set to "none". This means that the internal system decides the order of keys to optimize parsing speed. The order of keys in this mode should not be considered stable, and it's recommended not to rely on key ordering as it may change in future updates without notice.
    

    Setting propertyOrder to "input" ensures that the keys are ordered as they appear in the input during the decoding/encoding process.
    

    Example (Synchronous Decoding)
    

    import { Schema } from "@effect/schema";
const schema = Schema.Struct({
a: Schema.Number,
b: Schema.Literal("b"),
c: Schema.Number,
});
// Decoding an object synchronously without specifying the property order
console.log(Schema.decodeUnknownSync(schema)({ b: "b", c: 2, a: 1 }));
// Output decided internally: { b: 'b', a: 1, c: 2 }
// Decoding an object synchronously while preserving the order of properties as in the input
console.log(
Schema.decodeUnknownSync(schema)(
{ b: "b", c: 2, a: 1 },
{ propertyOrder: "original" },
),
);
// Output preserving input order: { b: 'b', c: 2, a: 1 }
    

    • 






... (truncated)





Changelog

Sourced from @​effect/schema's changelog.




0.67.22


Patch Changes



0.67.21


Patch Changes



0.67.20


Patch Changes


    

  • 

    #2926 4c6bc7f Thanks @​gcanti! - Add propertyOrder option to ParseOptions to control the order of keys in the output, closes #2925.
    

    The propertyOrder option provides control over the order of object fields in the output. This feature is particularly useful when the sequence of keys is important for the consuming processes or when maintaining the input order enhances readability and usability.
    

    By default, the propertyOrder option is set to "none". This means that the internal system decides the order of keys to optimize parsing speed. The order of keys in this mode should not be considered stable, and it's recommended not to rely on key ordering as it may change in future updates without notice.
    

    Setting propertyOrder to "input" ensures that the keys are ordered as they appear in the input during the decoding/encoding process.
    

    Example (Synchronous Decoding)
    

    import { Schema } from "@effect/schema";
const schema = Schema.Struct({
a: Schema.Number,
b: Schema.Literal("b"),
c: Schema.Number,
});
// Decoding an object synchronously without specifying the property order
console.log(Schema.decodeUnknownSync(schema)({ b: "b", c: 2, a: 1 }));
// Output decided internally: { b: 'b', a: 1, c: 2 }
// Decoding an object synchronously while preserving the order of properties as in the input
console.log(
Schema.decodeUnknownSync(schema)(
{ b: "b", c: 2, a: 1 },
{ propertyOrder: "original" },
    

    • 






... (truncated)





Commits






Updates effect from 3.0.1 to 3.3.1



Release notes

Sourced from effect's releases.




[email protected]


Patch Changes


    

  • 

    #2952 eb98c5b Thanks @​KhraksMamtsov! - Change Config.array to return Array<A> instead of ReadonlyArray<A>
    

    • 

  • 

    #2950 184fed8 Thanks @​gcanti! - Ensure Chunk.reverse preserves NonEmpty status, closes #2947
    

    • 

  • 

    #2954 6068e07 Thanks @​jessekelly881! - Fix runtime error in Struct.evolve by enhancing compile-time checks, closes #2953
    

    • 

  • 

    #2948 3a77e20 Thanks @​gcanti! - Remove unnecessary === comparison in getEquivalence functions
    

    In some getEquivalence functions that use make, there is an unnecessary === comparison. The make function already handles this comparison.
    

    • 



[email protected]


Minor Changes


    

  • 

    #2837 1f4ac00 Thanks @​dilame! - add Stream.zipLatestAll api
    

    • 

  • 

    #2837 9305b76 Thanks @​mattrossman! - Add queuing strategy option for Stream.toReadableStream
    

    • 

  • 

    #2837 0f40d98 Thanks @​tim-smart! - add timeToLiveStrategy to Pool options
    

    The timeToLiveStrategy determines how items are invalidated. If set to
"creation", then items are invalidated based on their creation time. If set
to "usage", then items are invalidated based on pool usage.
    

    By default, the timeToLiveStrategy is set to "usage".
    

    • 

  • 

    #2837 b761ef0 Thanks @​tim-smart! - add Layer.annotateLogs & Layer.annotateSpans
    

    This allows you to add log & span annotation to a Layer.
    

    import { Effect, Layer } from "effect";
Layer.effectDiscard(Effect.log("hello")).pipe(
Layer.annotateLogs({
service: "my-service",
}),
);
    

    • 

  • 

    #2837 b53f69b Thanks @​dilame! - Types: implement TupleOf and TupleOfAtLeast types
    

    Predicate: implement isTupleOf and isTupleOfAtLeast type guards
    

    • 

  • 

    #2837 0f40d98 Thanks @​tim-smart! - add concurrency & targetUtilization option to Pool.make & Pool.makeWithTTL
    

    This option allows you to specify the level of concurrent access per pool item.
I.e. setting concurrency: 2 will allow each pool item to be in use by 2 concurrent tasks.
    

    • 






... (truncated)





Changelog

Sourced from effect's changelog.




3.3.1


Patch Changes


    

  • 

    #2952 eb98c5b Thanks @​KhraksMamtsov! - Change Config.array to return Array<A> instead of ReadonlyArray<A>
    

    • 

  • 

    #2950 184fed8 Thanks @​gcanti! - Ensure Chunk.reverse preserves NonEmpty status, closes #2947
    

    • 

  • 

    #2954 6068e07 Thanks @​jessekelly881! - Fix runtime error in Struct.evolve by enhancing compile-time checks, closes #2953
    

    • 

  • 

    #2948 3a77e20 Thanks @​gcanti! - Remove unnecessary === comparison in getEquivalence functions
    

    In some getEquivalence functions that use make, there is an unnecessary === comparison. The make function already handles this comparison.
    

    • 



3.3.0


Minor Changes


    

  • 

    #2837 1f4ac00 Thanks @​dilame! - add Stream.zipLatestAll api
    

    • 

  • 

    #2837 9305b76 Thanks @​mattrossman! - Add queuing strategy option for Stream.toReadableStream
    

    • 

  • 

    #2837 0f40d98 Thanks @​tim-smart! - add timeToLiveStrategy to Pool options
    

    The timeToLiveStrategy determines how items are invalidated. If set to
"creation", then items are invalidated based on their creation time. If set
to "usage", then items are invalidated based on pool usage.
    

    By default, the timeToLiveStrategy is set to "usage".
    

    • 

  • 

    #2837 b761ef0 Thanks @​tim-smart! - add Layer.annotateLogs & Layer.annotateSpans
    

    This allows you to add log & span annotation to a Layer.
    

    import { Effect, Layer } from "effect";
Layer.effectDiscard(Effect.log("hello")).pipe(
Layer.annotateLogs({
service: "my-service",
}),
);
    

    • 

  • 

    #2837 b53f69b Thanks @​dilame! - Types: implement TupleOf and TupleOfAtLeast types
    

    Predicate: implement isTupleOf and isTupleOfAtLeast type guards
    

    • 

  • 

    #2837 0f40d98 Thanks @​tim-smart! - add concurrency & targetUtilization option to Pool.make & Pool.makeWithTTL
    

    • 






... (truncated)





Commits






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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
    • 

  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
    • 

  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
    • 

  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
    • 

  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
    • 

  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    • 




    

  
  



      


          

          
  

    
  
    
    

  

  




          

        
      




  





       
            



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the effect group across 1 directory with 3 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          b3efde1
        
      

    

  

    

      
Bumps the effect group with 3 updates in the / directory: [@effect/platform](https://github.com/Effect-TS/effect/tree/HEAD/packages/platform), [@effect/schema](https://github.com/Effect-TS/effect/tree/HEAD/packages/schema) and [effect](https://github.com/Effect-TS/effect/tree/HEAD/packages/effect).


Updates `@effect/platform` from 0.49.3 to 0.57.0
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/platform/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/@effect/[email protected]/packages/platform)

Updates `@effect/schema` from 0.66.1 to 0.67.22
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/schema/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/@effect/[email protected]/packages/schema)

Updates `effect` from 3.0.1 to 3.3.1
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/effect/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/[email protected]/packages/effect)

---
updated-dependencies:
- dependency-name: "@effect/platform"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
- dependency-name: "@effect/schema"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
- dependency-name: effect
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
...

Signed-off-by: dependabot[bot] <[email protected]>

    







  








      

  
            

    

      
    

    


      

          @dependabot
dependabot
bot



          added
  the 

  dependencies

  Pull requests that update a dependency file
 label


      Jun 10, 2024

    

  



  

  

    
  


  

      

    @dependabot
dependabot
bot


    mentioned this pull request
    
      Jun 10, 2024
    





  


  

      
   Closed

  







  









      

  
      



  

  @dependabot

    
      Dependabot
    




  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  Author


  


  

    

      

      
            dependabot
  bot

      

      

      commented

        on behalf of github

        Jun 17, 2024


      
    


  





      


        


  
    

      
          
Superseded by #226.

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
            

    

      
    

    


      

          @dependabot
dependabot
bot



            closed this


      Jun 17, 2024

    

  


    


  

  
  

  
      @dependabot
  dependabot
bot

    
    deleted the
    
      
        dependabot/npm_and_yarn/effect-4a5b835124
    
    branch

    June 17, 2024 14:12    
    













  
  

    

      

  




    


    

      

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



      

    

  




  
          




      

  

    
    

    
  

    Reviewers
  


    

    No reviews






    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

      

    dependencies

  Pull requests that update a dependency file








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    
      

        
    

    Development
  



          


Successfully merging this pull request may close these issues.



  


    
  




      

    

  
      

  

    

      0 participants